Hello,

Did you or anyone else here figure this out? This would be very useful.

Wilmer

HI Wilmer, from what I know, when you do a patch from a table, sage x3 look to .FIL file, and in this file, there is no way to protect using active codes, because of that, always you do a path with table, every column on table will go on patch, and this could be a problem.

What I do is always to do the path on client enviroment, or in a clean base, and after that I delete the columns, and keep the base clean, and keep one path file just for table.

Hi! Could you clarify if I understand you correctly?

You let the patch create as normal, and then edit the patch to remove all the non-activity coded fields? So like, if I made a field "YBIGNUMBER" you would delete everything from the table definition part of the patch so that only the 1 field is left?

Hi mhenson, no, if you do that, when you apply the patch, all the other fields will be removed from the table, and this will be problem to you.

Always when you create a table patch, x3 will get all the fields, indifferent the activity code, so, if you want just to sent the specific field, the best option to you, it's to add the field in a seed base, do the patch and then apply in the new folder.

OK! Thank you for that - I believe I now understand what you mean. Thank you for responding so quick before I tried my bad idea out lol

Yes it is possible. 

For table fields use the type 'ATZ' and the object name as (CODFIC='<TABLENAME>' & CODZONE='FIELDNAME')

For Indexes use the type 'ATI' and the object name as (CODFIC='<TABLENAME>' & CODIND='<INDEXNAME>')

This will palce them in the structure but won't validate the tables to bring them into SQL.  This might be possible by creating and 'EXE' object script.