Hello Everyone,
I need a flow that will validate an email-subject to a customer asset name.
Example :
Email subject : ROUTER ABCD down.
I want that Flow check if ABCD is a customer asset and if it is, to open a case on the right account associated to this asset.
Regards!
Solved! Go to Solution.
In the trigger, you do not want to use subject filter at all for your scenario unless you are getting other email as well, if this mailbox is dedicated to these emails then you would want to process them all.
I do something similar to extract an ID out of the email for example my subject is something like this:
How far have you gotten?
Where are the list of equipment stored? SharePoint list?
You can use odata query:
Asset eq 'ABCD'
you need to grab ABCD from the subject, i suggest you format the email maybe some it has a character around it so that you know 100% you are grabbing the correct value etc.
- The list of equipment is in Dynamic 365 Customer Asset
I would like the system to match the email subject defined field to the D365 Customer asset.
The Odata asset eq is not existing.
Hi,
I am sorry i have not done anything with D365 but, the first thing you will need to do is figure out the field name.
looks like perhaps it is: msdyn_name
In the trigger, you do not want to use subject filter at all for your scenario unless you are getting other email as well, if this mailbox is dedicated to these emails then you would want to process them all.
I do something similar to extract an ID out of the email for example my subject is something like this:
Proud to be a Flownaut!
I guess it would work if my Message Id would increment and not if the subject is always the same. Since I can get the same alert 1000 time, it says "record already exist". therefor Message Id is not right But......................
I used your expression into my msdyn_name expression and it works great.
Thanks alot!
Join digitally, March 2–4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!
User | Count |
---|---|
84 | |
60 | |
54 | |
44 | |
40 |
User | Count |
---|---|
85 | |
81 | |
76 | |
62 | |
42 |