Power Automation (Flow) send email with Image from Picture Field (Sharepoint list)

 The Scenario - When item is created in list B, and list B has the ID for item in list A, go get list A item by id, where there are some details including a Picture field, and send all that via email.

The main thing to remember is that MS did not develop the api needed for the flow to get the picture field, so we cant read nor update it, only via HTTP.

Steps:

  1. trigger when item created in list B
  2. parse listItemB_ID field from float to integer
  3. get item from list A via flow
  4. get item from list A via HTTP request to SharePoint (*not premium)
  5. get the Picture field value, it's a JSON
  6. parse that json
  7. give a schema for the parser
  8. where do we find the sample for the schema
  9. build the Picture url
  10. send email

1. trigger when item created in list B


 
2. parse listItemB_ID field from float to integer

the item A id field, although set to be integet, is eventually a float for the flow. we must parse it using the `int` function, using 
int(triggerOutputs()?['body/CouponID'])



3. get item from list A via flow 

This is actially a duplicate, steps 3 and 4, and I could've just get the item via HTTP and parse that response, but I was lazy, and happy to have an example for both.
Also its nice to have Get Item, singular, there used to be only Get Items, plural, and then you needed to extract the item.


4. get item from list A via HTTP request to SharePoint (*not premium)

This step they lately took out from premium, unlike other HTTP requests.
_api/lists/GetByTitle('CouponsList')/items('@{variables('CouponID')}')



5. get the Picture field value, it's a JSON

I actually had to manually write this down
outputs('Send_an_HTTP_request_to_SharePoint')?['body/d/CouponBackGround']



6. parse that json

The JSON parser is great, you must provide a schema. It sounds scary but its not, just take the JSON from last step (run the flow), click on "Generate from sample", paste and "done".



7. give a schema for the parser

That's how it looks.



8. where do we find the sample for the schema

When you run the flow, that's how it looks, the JSON response, copy paste it as instructed in step 6.




9. build the Picture url

The JSON of the image actually contains seperatly the serverUrl (the tenant) and the rel url for the image, so you need to pick them both.
As you can see, once you parse a json result its very easy to use it, and you dont need anymore the "Get Item" step.



10. send email

You must use the Image Tag in HTML mode.



Have Fun!

P.S. - at the client's tenant, Get Item failed for the Picture Field... so lucky me I used the HTTP results :)

Comments

Post a Comment

Popular posts from this blog

OverTheWire[.com] Natas Walkthrough - JUST HINT, NO SPOILERS

game portal: http://overthewire.org/wargames/natas/ PASSWORDS for each level are stored in /etc/natas_webpass/natasX I made this walkthrough for people like me, i needed some help, but didnt want the spoiler, so here i will give you all the information needed to pass each level, yet not the solution. For levels needed custom web request i made a different post for powershell and javascript  with how-to's, since is a piece of learning for itself, and also for those of us that play at work and have only powershell at their hands. Although its not a complete spoiler there, its quite most of the solution so try yourself 1st. Natas The Natas game is from basic to advances web hacking. Every few levels is about whole new exploitation (with some harder ones doing comeback later), so a lot of learning. If you're new, you're the reason i am writing so much even for the 1st level, just please google EVERY topic you see, since in the following levels i assume you know the
Read more

Asp.Net Ending Response options, Response.End() vs CompleteRequest()

this blog is for any1 who get the ThreadAbortException when caling Response.End(), and then tried the other options such as HttpContext.Current.ApplicationInstance.CompleteRequest() and found out that there was no replacement. i'll start with the bottom line: if you want to stop right now your response and send it as is you dont have any other option other than Response.End(), period and it's the right thing to throw that EX in that case. the answer is its because there is the "HTTP pipeline" and the "Asp.Net pipeline", and CompleteRequest() cuts the HTTP pipeline but not the Asp.Net one so everything that is from handlers forwars (including all page events) continues but your part, the asp one, stays in your hands so that no information will be lost, so ur suppose to manage your code currectly, since information lost is really a bad thing, although in most cases we use Response.End() we know what we are losing and we want it. see this short article ab
Read more

SOLVED The item could not be indexed successfully because the item failed in the indexing subsystem

if you got an error like this The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Failed to recover content group; Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 04081656-B51B-4DCD-96D4-6DB2D2CEEEE7 ) as well as these: The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Caught exception when preparing generation GID[7]: (Previous generation (last=GID[6], curr=GID[7]) is still active. Cannot open GID[7]); Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 92EB0180-C086-4853-BED8-F4878D9748AD ) the solution for me was to clear configuration cache (PS)  and then restart SP Search Services. THX to m
Read more