Impact of Missing system="yes" Attribute

[Brian Collins]

ACPROD is an AM database that was upgraded from 5.12 to 9.3.  In the XML file exported from ACPROD, there are a number of links and tables with the system="yes" attribute.  For example:

  <link name="ESDDelivMethod" sqlname="ESDDelivMethod" system="yes" card11="yes" type="Neutral" usertype="Normal" srcfield="lESDDelivMethodId" desttable="amESDDelivMethod" destfield="lESDDelivMethodId" reverse="Action" />

ACPLY is another 9.3 AM database that started with the same schema as ACPROD.  At one point it also had the system="yes" attribute on many of its links and tables.  A developer has made changes to ACPLY and now the schema in the XML file no longer has the system="yes" attribute on its links and tables.   For example:

  <link name="ESDDelivMethod" sqlname="ESDDelivMethod" card11="yes" type="Neutral" usertype="Normal" srcfield="lESDDelivMethodId" desttable="amESDDelivMethod" destfield="lESDDelivMethodId" reverse="Action" />

What is the impact of removing the system="yes" attribute from the ACPLY links and tables?  If we apply the ACPLY schema to ACPROD, will the missing system="yes" attribute impact the APROD database now or in the future?

Thank you in advance for any information that you can provide.

[Jason_Dowd · Accepted solution]

Hey Brian,

The system="yes" attribute isn't used anymore in 9.32. In fact, its presence will actually cause issues if you try to do a diff between the custom structure and the system structure (stuff will get listed as system even though it's not). That's the only time it will cause issues, though. Most of the time you won't even notice. So I wouldn't worry about it unless the customer wants to do a diff, then in that case you want to get rid of ALL of the system="yes" attributes in the db structure.