"Escaping out" a comma from the name of a parameter when doing a search | Adobe Higher Education
Skip to main content
JohnJOSullivan
JohnJOSullivan
Level 6
January 30, 2025
質問

"Escaping out" a comma from the name of a parameter when doing a search

  • January 30, 2025
  • 2 の返信
  • 597 ビュー

This is a new one.

 

I'm working on an automation which determines all common paramterValues between an issue an a document. When it has its list, it plops the list into the output field of a search module and pulls those exact fields. 

 

Everything works...until a parameter has a comma in the name of it. 

 

If I do things the "normal" way and specifically select the name of the field, the system works correctly:

However, if I attempt to do this by entering the name of the field, Fusion gets confused. It thinks it's two fields instead of one and then Fusion errors out.

 

I know I have to "escape out" the comma using the text parser to make Fusion realize that it's actually on field instead of two. I'm trying to look at the output bundles but I'm not seeing something which stands out.

 

Any ideas?

 

2 の返信

JohnJOSullivan
JohnJOSullivan作成者
Level 6
February 4, 2025

Update: So I stopped trying to figure out to escape out a stinking comma and ended up re-writing the whole thing. 

 

Just like before, I had Fusion gather all the parameter names from the document. I needed those to use as a filter so Fusion would only grab information from the issue/project which can be placed on the document. 

 

Then, I did a custom API call to gather all parameterValues from the issue/project. I transformed it into JSON so I could be able to separate each parameterName/Value pair into its own line (e.g. "nameOfParameter":"parameterValue"). I did some text parsing to do this, then did a split() on the JSON. I added all of these lines into its own array.

 

Then, I iterated out the document parameter names. For each name, I iterated out all the parameterName/Value pairs to see which parameters also appear on the document. Anything that passed the filter got added to a new array.


Finally, I added some additional custom forms to the document, took the array, reconverted it into JSON, then did a custom API PUT command to add all of those parameterValues to the document. 

 

So hurray--only the fields which exist on the document get transferred from the issue/project. And it works very well.

 

And all of this because of a stupid comma. 😄 

 

 

    Sven-iX
    Community Advisor
    Sven-iXCommunity Advisor
    Community Advisor
    March 17, 2025

    Hey John,

    Couple questions: Why did you manually map the fields like in the screenshot? If you select checkboxes that would work - no? 
    Mostly because I am lazy I got curious and wanted to send you my approach. I get the list of docs, then for each doc, i get the issue, compare the custom fields, and finally set a JSON object. Since I'm not typing any form field, it doesn't care whether a name contains a comma.
    If you have time, let me know what you think. 

    Oh - and I would always try to make the field names something short like "targetingMethod", or even "paid tagging or pixels"

     

    Cheers

      jon_chen
      Community Manager
      jon_chenCommunity Manager
      Community Manager
      April 2, 2025

      Hello @johnjosullivan,

      Could you please provide more context about your question? This will greatly assist our community peers and advocates in troubleshooting, which should help you receive an answer more quickly. Thank you!

      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity Manager
      Community Manager
      September 1, 2025

      @johnjosullivan just checking in! Were you able to get this resolved? If one of the replies above helped—whether it completely solved the issue or simply pointed you in the right direction—marking it as accepted can make it much easier for others with the same question to find a solution. And if you found a different way to fix it, sharing your approach would be a great contribution to the community. Your follow-up not only helps close the loop but also ensures others benefit from your experience. Thanks so much for being part of the conversation!

      Kautuk Sahni
      契約条件Accessibility statement

      Loading footer...