
Scott Henderson CTO
- Total activity 305
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 0
- Subscriptions 121
Activity overview
Latest activity by Scott Henderson-
Scott Henderson created an article,
Move flows between integrations
Unlike reusable resources such as exports and connections, a flow can be associated only with one integration. If you didn’t create the flow within an integration, or if you’ve already detached it ...
-
Scott Henderson commented,
Hey Steve, someone on my team will get back to you on this next week. I am thinking we should be classifying this error as an 'intermittent' error, and then we should be auto retrying on your behal...
-
Scott Henderson commented,
I think Matt was hinting at doing something like the following. Turn off your flow. Run your mass update in NetSuite. When the mass update is done, go an update 1 single item. Turn flow back on, a...
-
Scott Henderson commented,
You could always build a flow to export your mappings and send them to a CSV/excel document.
-
Scott Henderson commented,
If you need a response back, then you should follow the pattern on this page where you invoke an import directly via our REST API. https://docs.celigo.com/hc/en-us/articles/8213191419163-Invoke-an-...
-
Scott Henderson commented,
I recommend contacting customer support. If you want help from the community we need more info. Can you share screenshots of your flow, the import drawer, the error drawer, etc...?
-
Scott Henderson commented,
Can you share screenshots of your export so we can see exactly where the characters are being converted? Can you also share a screenshot of your connection so we can see the media type being used? ...
-
Scott Henderson commented,
Do you have the "Group rows" field unchecked? If "Group rows" is unchecked then I am confused by what is happening in the example you provided. If NetSuite returns 5 records, how does that turn in...
-
Scott Henderson commented,
Happy to help!
-
Scott Henderson commented,
I def like the idea of bringing the "One to many" concept into the source exports somewhere, and then also having the option to include fields from the parent record in the child records, and then ...