Celigo flow from BambooHR to Netsuite, I have a step to lookup NetSuite internal id by Bamboo Employee Id, however - I also need to lookup the Supervisor Internal id in netsuite - the Bamboo source record had supervisorIid - but I don't know where to ask celigo to match that to the netsuite saved search

AI generated answer (using internal Slack threads):

In Celigo, you can use the Lookup functionality to match the supervisorId from BambooHR to the corresponding NetSuite internal id. Here's a general idea of how you can do this: 1. In your flow, add a Lookup step after the source (BambooHR) and before the destination (NetSuite). 2. In the Lookup step, select NetSuite as the Lookup application. 3. Choose the appropriate NetSuite connection. 4. For the Lookup object, select Employee. 5. In the Lookup field, select the field in NetSuite that corresponds to the supervisorId from BambooHR. This might be something like 'External ID' or 'Employee ID', depending on how your system is set up. 6. In the Lookup value, select the supervisorId from the BambooHR source record. 7. In the Return field, select 'Internal ID'. This will return the NetSuite internal id of the supervisor. This will allow you to match the supervisorId from BambooHR to the corresponding NetSuite internal id. You can then use this internal id in subsequent steps of your flow. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******

Additional criteria would be where you specify it. You make a search, then in additional criteria you pass the id from the source record to it and it will only return the search results for that id (and or other criteria)

Thanks @Tyler Lamparter also sorted this - I am sure there is probably a better way than I did it, just added a lookup for specifically looking up Bamboo Supervisor ID and returning NS internal id for that record and writing it back to the source data, then move on to the look up step that gets NS internal id of the employee record (again writing back to source data) 🙂 (errors on import are just from folks that had started off in one sub & transferred to another)