
I now have this one GL integration that refuses to import all records. Out of about 1,000 it just misses 5% of them. The integration has a header and detail section. The query relationship is set to date, reference and jrnl. I have created the integration using both the GP source adapters and the eConnect adapters. For the ones it misses it will create the header but leave the detail blank. I have tried setting UseOptimizeFilter to False but that results in the dreaded 'UCASE' function error message. I have loaded the latest IM service pack. Has anyone else experienced this type of behavior with IM for GP 2013? Since it always misses the same ones I thought it was data driver. I run queiries in SQL on this data and all headers and details line up, even the one IM misses. I have even adjusted the queries to strip away blanks, ampersands and quotation marks.
*This post is locked for comments
I have the same question (0)Can someone explain exactly what this option called UseOptimizedFilters is supposed to do? After fighting with this integration, I thought it was best to make it a simple SELECT * from MYHEADERTBALE and SELECT * from DETAILTABLE. So I did all the stripping of non-alphanumeric characters first and created two separate work tables. I recreated the integration and once again it was skipping the same records. Now I then went and set the UsedOptimizedFilters back to False which it was in my other integrations and now all records are imported. So I learned a valuable lesson here. Keep your queries as simple as possible and do any data manipulation up front. But I really would like to know what the UseOptimizedFilters is supposed to do because it seems to cause a lot of grief.