multiple periods with same end date
This is the prebuilt validation check of eConnect – to ensure that date is not in a closed period. I am guessing that IM does that check differently (perhaps sees if it is in an open period – rather than looking to see if it is in a closed period).
Your best bet would be to open both periods for such an integration. Alternatively you are looking at wirting custom nodes for eConnect with different validation rules.
Since the users want to make sure data enters the right period they have been closing one, then loading data. Then they close it and open the other period then load data. Does nayone know of a way to force the GL tranactions into one period or the other if they both have same date using smartconnect?
You have me on that one – have need had a need to attempt that. I hope someone can help us.
If you would like to submit an answer or comment, please sign in to the eOne portal.