@baltazarrocha there are several ways you could do this.
- Use handlebar expressions on the mapping. You would have to keep adding to this handlebar expression as new things come up. This entire expression could be come quite large, but it would work. Here is an expression that works with what you've specified:
{{#compare (regexSearch Purchase_Order_Number "^DEN") ">" "-1"}}10276{{else}}{{#compare (regexSearch Purchase_Order_Number "^KCY") ">" "-1"}}10278{{else}}{{#compare (regexSearch Purchase_Order_Number "^MIN") ">" "-1"}}38675{{else}}{{#compare (regexSearch Purchase_Order_Number "^SLC") ">" "-1"}}10274{{else}}{{#compare (regexSearch Purchase_Order_Number "^STL") ">" "-1"}}10279{{else}}{{Real_Account_Number}}{{/compare}}{{/compare}}{{/compare}}{{/compare}}{{/compare}}
- You could use scripts as well that utilize form settings. This would be a bit more complex to initially setup, but would be better in the long run. Here are a few articles on how it works.
https://connective.celigo.com/t/querying-netsuite-records-in-custom-form-builder-settings/566
https://docs.celigo.com/hc/en-us/articles/360059205112-Common-form-fields#type_staticMap