table is getting to large

RalphW

The table sales header is getting to large (more than 4'000 Bytes) after adding various new fields required for additional functions.
Does anybody encountered the same Problem and what is the solution? Shadow table?
Thanks for any help und ideas
RalphW

RalphW

Thanks RaniShoura
I did try this, but cannot "disable" so many fields, that it would fit. On the other Hand, this Problem would occur with every update, where fields would be added from NAV.
Therefore I would like to fix it finally.

Do you have experience with shadow tables?

Best Regards

RaniShoura

The size restrictions is for active fields, you can disable fields that you are so confident won't be needed "Keep the disabled fields so you still could compile your code".

Please note that if the disabled field is used in any of your code paths, an error will be thrown. another disadvantage to this practice that if you wanted to get the disabled field feature to work later on you will have a headache getting things back to standard.

If I was in your show I'll always look in the new development design. and yes an option will be a parallel "shadow" table

hope this could help

RalphW

Thanks RaniShoura
I did try this, but cannot "disable" so many fields, that it would fit. On the other Hand, this Problem would occur with every update, where fields would be added from NAV.
Therefore I would like to fix it finally.

Do you have experience with shadow tables?

Best Regards

RaniShoura

The term as of my knowledge is not a technical term it is more of a design pattern, I had the same for T36 & T18 it is managed by function design records are synced using standard NAV triggers

RalphW

Hi RaniShoura
I am aware of this. I also have the problem with T36 (Sales Header). In order that I do not have to "reinvent the wheel", can you please let me have your T36 and the corresponding shadow table?
I would appreciate this very much.

RaniShoura

Unfortunately I can't share with you any part of our environment, still I'm more that happy to continue on this discussion. as a start you need to have a new table with the same key in T36 (Document Type, Document No.) , now depends on the use case you need to work the insert triggers (Do you want a shadow record for each rec in 36?) if yes you have to code the same in T36 insert trigger, you need to do the same for delete ....

Then you have to work on posted tables, CU Form Designs and reporting...... this is all related to what function you are working on