You’re offline. This is a read only version of the page.
Announcements
We are combining two companies into one and I am having a problem.
When using integration manager to pull in a month of GL to the new company the accounts and debits and credits are blank for day 10 to the EOM. If I split the batch into day 1-9 and 10-EOM then both batches are OK.
But it consistently messes up from day 10-EOM when trying to pull in the entire month. Using eConnect version.
We are running Dynamics v10.00.1061 and IM v10.00.1384
Has anyone else run into this and did you find a fix?
Thanks in advance
Todd
*This post is locked for comments
It is a fix but, I still think they need to look at the eConnect procedure that is being used. It seems that when it changes from a single digit day to a 2 digit day it starts skipping the distributions. That is what was very consistent. I have no special characters in the table. This has happened to a co-worker who also works with GP and integration manager and it was exactly the same, day 9 to day 10 and the distributions are gone. He simply split it up into two batches and gave up.
Victoria, I checked the short date settings and they are the same.
Thanks for listening.
Todd
Great stuff Todd. Thanks for posting the MS response. One to remember for the future...when all else fails, switch off UseOptimisedFiltering...
Best regards,
I ended up calling microsoft on the issue and I am including their response which did fix the problem. I have looked through my data and found no unusual characters so I am not exactly sure what this setting is doing. To answer the other question, the header for days 10-EOM are there, just no distributions.
ASSESSMENT:
==================================
Thank you for taking my call and streaming today. We reviewed your integration and your SQL table you are pulling data from. We saw that you have the relationship and the Group bys set on Journal ID, Batch ID, and Trx date.
We verified that your version of GP is 10.00.1061 and your version of IM is 10.00.1384.
We queried the table and saw you have 2,200 journal entries and approximately 19,000 rows of distributions.
We narrowed down the SQL table to only the days 9 and 10 and were able to recreate the issue.
We then changed your Useoptimizedfiltering from True to False.
This resolved the issue.
As discussed this setting, when set to true will speed the integration as it ignores any sorting you have on the integration. There is limited information on this setting so if we suspect an issue with an integration such as this issue we generally at least test changing that setting and running the integration again.
When setting UseOptimizedFiltering to False, the integration becomes a lot less particular about your source file. With it set to True, the source file must be exact and have no special characters (&^%$#@!~, etc) or it won't see the relationship as valid. You were using one SQL table for your queries so this may be due to special characters within the distribution reference field or possibly the column header itself.
Also not sure I can help without actually seeing the data and the setup...however one thing that comes to mind when I hear that something breaks after day 9 is to check the Short Date format in the Regional Settings on the computer where you are running IM and compare it to what the SQL Server Short Date setting is.
Hi Todd,
Not sure I can help, but your post has been unanswered for a while, so...
If you run a full months transactions, does the journal get created in GP?
If it gets created is it the case that you get lines with accounts and amounts for the first 9 days...and then lines with just accounts for the remainder days up to EOM?...or what? (I think from your post that if you integrate a full month, onle th first 9 days get created...and this is all that comes into the journal).
Ian.
#1
André Arnaud de Cal...
293,435
Super User 2025 Season 1
#2
Martin Dráb
232,567
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (