Issue with API Call in Scenario | Community
Skip to main content
DeborahLeigh123
DeborahLeigh123
Level 4
April 4, 2025
Solved

Issue with API Call in Scenario

  • April 4, 2025
  • 2 replies
  • 826 views

Greetings All - I am new to API Calls and I almost have this scenario complete. However, I'm having an error message issue and don't know how to fix it.

 

Here's the scenario - I'm copying fields from one Custom Form to another. The fields are exactly the same. However, it's causing the attached error. I think it's because I'm copying it from An issue object into a program object.

Here's what I think it is...but I'm not entirely sure:

  • Verify Custom Field Configuration: Do I need to use DE:<customFieldName> instead? If so, which module would I need to update?
  • Update the API Version: Do I need a newer API version in Fusion? If so, how would I do that? Is there any documentation out there?
  • Is there another option I'm not seeing?

Thank You for your help in advance! Deborah

Best answer by Sven-iX

Ah - in your name/value pair module, add DE:  to the value of "Field Name"
Then your scenario works fine. 

 

Couple unsolicited comments: 

  • If you want ALL fields copied you don't need to know what form they're on - so arguably you don't need the category/categoryParameter modules. 
  • you don't need the setValue #7 - you can just use the #6 output JSONstring
  • You may want to create a connection to WF that is not your user but a generic "service account" 

2 replies

Sven-iX
Community Advisor
Sven-iXCommunity Advisor
Community Advisor
April 7, 2025

Your error is in the last module - could you show the configuration? 

If you're updating a normal object with form - why are you using customAPI calls and data transformation instead of reading all parameterValues and mapping them to an UpdateRecord module? 

DeborahLeigh123
DeborahLeigh123Author
Level 4
April 7, 2025

Yes of course! Please see attached. I Did want to make mention I'm taking form fields from an Issue inside a Project Queue (Program, Project, Task, Request config) and pasting it into a designated Program with a different form, but the same fields. 

 

Please see attached. TY Deb

DeborahLeigh123
DeborahLeigh123Author
Level 4
April 8, 2025

Hi Deb,

all is good in that module since you're using the JSON generated in module #7. 

Yes I would first try and use DE: for the custom fields.

 

Second I would try to get the Issue/Request with "parameterValues" (added to the list of fields to return) and map them to the program form. 

In the case you want to stick with what you have, try the DE: addition first, if that fails lets' see the JSON object? 

 


Greetings. Not quite yet. I was unable to find anything missing that you suggested. I put together all the fields to show you I was calling parameterValues and DE: Do you spot anything unusual in there? I attached an image. TY

Sven-iX
Community Advisor
Sven-iXCommunity AdvisorAccepted solution
Community Advisor
April 8, 2025

Ah - in your name/value pair module, add DE:  to the value of "Field Name"
Then your scenario works fine. 

 

Couple unsolicited comments: 

  • If you want ALL fields copied you don't need to know what form they're on - so arguably you don't need the category/categoryParameter modules. 
  • you don't need the setValue #7 - you can just use the #6 output JSONstring
  • You may want to create a connection to WF that is not your user but a generic "service account" 
DeborahLeigh123
DeborahLeigh123Author
Level 4
April 9, 2025

@sven-ix You're the GOAT! TYVM for your time. your solution to add DE: was the golden ticket. 

I actually do need the entire string because it will be pasting into a different custom form. So, keeping the original string is correct.

 

Thank you very much! Deborah

Terms & ConditionsAccessibility statement

Loading footer...