This just came up and I am guessing it has something to do with our changes to the form. We have customized the PO Form and we have PO with large header comments and 263 Lines. I am getting the following error when I try to print the PO. The base form prints fine.
Kimberley,
Others have said this is caused by including too many columns. If you added a table to the report data definition ensure that you are only including necessary columns. That goes for the rest of the tables as well.
-Utah
I have definitely only added the columns needed to the added tables. I know that has bit me before, when Epcior added Every column that wasn’t needed. Just frustrating that I have been almost a year on this form and all of a sudden I have an error.
it looks like one or more of the fields.value within the added columns has/have got more characters (counts) than what the table field defined to handle.
1 Like
Updated: Oh wait so it is based on the field is defined.
I was thinking it was the PO Header Comments…It is huge.
The count is 4838 characters…I honestly thought this was the issue. How can I tell how much space i have and can I give it more? (not sure I asked this correctly)
Kimberley,
In these cases I go through the data definition and suppress any field not being used in the report. Have to be very careful with that as some fields may be hidden.
Safe bet is to first remove most labels first from any table you’ve added.
The issue is that SQL tables have a limit to how many fields show up, not how many characters are in the field. It is a hard, built in limit, which cannot be adjusted.
I definitely don’t have any fields in the table that are not needed.
I have not tables added to the PO Form. I will try removing the extra fields on Data definition but I know this have bit me before too. I wish it would tell you the field in the error.
thats is right, what ever defined originally can not be changed, unless if it is UD fields because it will be defined as Max by default (maximum in SQL approximately up to 2 GB), and you can find this in MSSMS for example ShipName field in POheader table can not handle more than 50 string characters in my SQL database instance
Kimberley,
I did not read the error message thoroughly. @A.Baeisa is correct, it is a field size limit issue. Try to print the report with a test PO which does not have the extra comments. If that prints, you know where the issue is. Its a process of elimination at this stage.
1 Like
I am working in my TEST DB…I have removed all comments from the PO Header and that didn’t do it…I will check the PO Detail Comments…
and make sure that all Db tables are synchronized
I don’t think it is my comments…I think it is my Qty field.
If a report fails how do I get the guid(?) to run the report in SSRS?
I know where I can get it for the reports that don’t fail.(screen shot to show what I am talking about in case I didn’t explain it correctly)
If I run the PO form in base form and use that guid on my custom form I get an error…should I be able to use this guid on my custom form…I thought I could…here is the error…Is this my problem???
Sometimes that might work, but if your data definition and data in SSRS report are different, the report expects a field that may not exist in the data, which will cause an error.
so how can I test it in SSRS to see if I get an error on this form in SSRS?
I was thinking I could get he info from SQL SSRS DB but can’t remember…been too long and haven’t touched SSRS in months.
Does this problematic style use a different RDD than the base style?
Check your UD fields first. Make sure any new UD fields have been synchronized with the DB. My next step would be to retrace the steps if it’s not a huge deal to isolate which fields are causing this issue. You can copy the standard report and data definition. Link the new report style and data definition together. Then add the table you previously added, but only show fields required to link the new tables together, such as “Company”, “OrderNum”, “OrderLine”, etc. Synchonize the report style and data definition and test. If it tests ok, add only the fields you need and test again. It will help to isolate the issue.
That’s one approach. It really depends on how far along you are on this custom report.
OH my GOD…That will be a huge project. I have no idea all the changes that were made to that form. My UD feilds are synch and fine…there are only a couple and none new. the the key is other POs work fine it is just his one.
Hi Kimberley,
Based on your original error, i think your problem is in the PO header, not line (quantity), per highlight.
I haven’t worked in SSRS in awhile either but do recall entering the GUID to make it run with my data.
I wonder if you queried the same data directly on the SQL server if it would provide clue.
Nancy