Hello everyone!
Im trying to automate a Custom Field in JSM from a Microsoft List. In the list we have 150+ locations which I want to be able to select in the Custom field.
I have set up a Power Automate flow, connected the list and got GET and POST to work, however im not sure this is the best approach? I also want to be able to Delete and change an entry if its name is updated in the list (post will only add a new entry if the name is changed)
Current Setup:
Power Automate flow, connected to MS List.
Trigger: "When an item is Created or Modified" -> HTTP with GET -> HTTP with POST (successfully adds new entries but doesnt change name or delete entries)
Using URI: rest/api/3/field/customfield_100xx/context/102xx/option which get my CustomField including the Values.
(more specific:
"id": "10147",
"value": "TestLocation",
"disabled": false
If anyone has any experience with this, I'll gladly listen to ideas!
Cheers!
API options to change are available, see:
You have the option to POST and GET (as you use), you will need to use the PUT option.
Hi @Marc - Devoteam Thank you for your reply.
I have seen the documentation and tried to apply everything needed. Im probably not smart enough :)
What I cant get my head around is that to delete an entry, I need to have two values, both the ID and the Name. And compare the values between the MSList and whats already in the API list somehow.
I don't know very much of JSON scripting..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Why delete an entry?
This will remove the information from the Jira issue, best practice is to disable the option, then it can't be used anymore on a JIra issue, but it wil retain the information for searching and maybe reporting.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Marc - Devoteam oh Thank you, I didnt think of that. Was exacly why I asked in the first place to get some good practises along with suggestions.
I agree that deleting will also remove valuable information, will look into PUT and disabling the options instead of removing!
Again, thank you for your responses :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please accept my answer as a solution, if my answer helped to solve your request.
This will help other community member trying to solve the same.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Marc,
Thanks, I haven't got the chance yet to fully get this working.
The solution might be in your suggestion yes, as it links to the API documentation
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please accept my answer as a solution, if my answer helped to solve your request.
This will help other community member trying to solve the same.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Still havent got this working, but the answer is most likely in there.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.