Hello! Looking for some help w/ Celigo <Integrator...
# general
a
Hello! Looking for some help w/ Celigo Integrator.io I'm trying to create a flow to find transactions in a range of GL accounts that are missing Dept & Location, and populate them with the correct values. I'm testing all of this out in our sandbox, and my NetSuite connection in Celigo is using my Administrator credentials. I keep getting the following error even though I've turned all "Allow Non-G/L Changes" for each month in FY2022, the test transaction date is November 2022, and I'm in an admin role, so I'm not sure why the error is persisting. "Failed to save record because You cannot make changes to this period. You need the Allow Non-G/L Changes permission and must set the Allow Non-G/L Changes preference in the period record."
s
I would suspect that the period in question is completely closed - you would see a green check mark in the period closed column in the accounting periods list. If so you would need to open the periods again. Even as an admin you cannot access periods that are completely closed.
a
@Simon Whittle thank you but I definitely made sure all months in 2022 are open & the allow non-g/l changes is checked
s
I would suggest trying to make the same change celigo is attempting through the UI manually and see what happens. It would make no sense if the celigo connecting account is an admin and the periods are open. My only other thought is celigo is grabbing a transaction outside of 2022
a
I was able to edit the vendor bill (test transaction) just fine no issue
s
I would also double check that celigo is actually hitting the SB and not prod.
sorry these are obvious but I don't know what else it could be based on what you are saying
a
lol right that's why I'm so confused, I've built flows much more complicated than this before
nevermind I got it! It had to do w/ the filtering of how Celigo finds the transaction - I needed "Internal ID" not "Internal ID (Number)"
s
ah, it was hitting a transaction in a closed period and not the trx you were expecting
a
yeah that sounds about right, only reason I figured that out is by looking @ the response data and had an unusually short Internal ID# to be a 2022 transaction