Is anyone else having problem adding new tables into the ARForm data definition? We have just switched to 10.2.200.3 (from 10.0.700) and as soon as I add a table (OrderHed link to InvcHed with Company and OrderNum), when I try and print, using the new RDD, I receive error telling me query exceeded 1024 columns. This happens even if I exclude all columns from the newly added table.
Here is the error:
Program Ice.Services.Lib.RunTask raised an unexpected exception with the following message: RunTask: CREATE VIEW failed because column âSignatureText02â in view âRptLabels_C5E65FDD401E4369B120C9CDF6B86292â exceeds the maximum of 1024 columns.
I experienced that giant pain in my rear the whole day and night yesterday!! I kept excluding columns I thought are not used and I still got the error. At some point the error changed to missing Calc_⌠fields where I never excluded a calculated field.
I think I should have clicked on Sync datasets after the exclusions. Something I didnât do and will have to do today and see if it makes any difference.
aidacra
(Nathan your friendly neighborhood Support Engineer)
8
Donât ever is too strong. That button isnât a magic bullet to getting the one new column you want into the dataset in the RDLâthe sync dataset logic is very complex and can sometimes cause unexpected behaviors.
It is generally simpler / better / more optimal from a performance standpoint to manually add the column in the dataset within the RDL than to use the Sync dataset button.
EDIT 1: As an aside, there is a discussion happening right now within Epicor about this functionality, and there are very strong opinions on all sides of the issueâI have very strong opinions about this functionality. Our objective with the sync dataset was pure and good, but, due to the complexity of our report assemblies it isnât within technical possibility for the sync dataset to do what people think it does/should do with our reports the way they are.
EDIT 2: To paraphrase Joshua 24:15 (speaking for myself), âas for me and my house, we willâ manually edit the dataset instead of using the sync dataset button.
But you cannot exclude a column that is referenced in a table relationship.
So if the original RDD has InvoiceNum as a field, and you add the InvcHead table, linking the InvoiceNum fields, you must still include InvcHead.InvoiceNum, even though it will be a dup of OriginalRddTable.InvoiceNum
I hope you changed itâs size and or moved it âoff the edgeâ. Leave it there, but make you have to work for it to use it
Iâve clicked it by accident when I thought I was on the SSR Break/Routing tab, and meaning to click the âDesignâ button. Luckily I didnât mindlessly blow through the warning that pops up when you click âSyncDatasetâ
A scripture reference nice. Joshua 25:15 is a verse my wife and I live by for our home.
as I am running into what appears to be a similar issue as i have seen in the post and hoping you are someone has an Idea as I have not heard back from Epicor on this
Program Ice.Services.Lib.RunTask raised an unexpected exception with the following message: RunTask:
System.ArgumentException: Column âCalc_DspDocLineTaxâ does not belong to table InvcDtl.
I do not see that field in the RDD that field I did not see in our old version or new one. Any thoughts on this?
This is the last post Iâll necro I swear! âŚjust doing the top search results for the issue.
I fell into the trap of providing the same intuitive advice as the others here on another post without truly investigating AR Invoice. There appears to be an oversight / (possible enhancement opportunity) related to AR Invoice CSF I mention here: