I get the idea of packages, and have managed to move them from one system to another, but I am not sure I am creating them "correctly"
What ItemTypes should be in the packages? RelationshipTypes for instance. Do I include the ItemType for the RelationshipType? The Aras packages don't seem to.
Thanks in advance,
Andy
Hi Andy,
This is a tough question to answer, because my answer changes based on the version of Aras Innovator or solution you are working with. I can, however, try to give a list of the Core ItemTypes that make up the basic metadata of a database. This is NOT a definative list, but should act as a helpful guideline when creating your packages.
Actions
E-Mail Messages
Forms
Grids
Identities
ItemTypes (Exclude ItemTypes with is_relationship=1)
Life Cycle Maps
Lists (Exclude Lists associated with PolySources like “Change Controlled Item” and “Deliverable”)
Methods
Permissions
RelationshipTypes
Reports
Sequences
SQLs
Workflow Maps
Try to think of this list as a checklist when you ask yourself, "Did I miss anything?"
I hope it helps!
-Bill
Here's a question. If you include Sequences in the package, then the Sequence objects are exported as they are in the development, system, right?
That means that if you re-import the package onto a production system, you'll overwrite your Sequence numbers and reset them to some old value, causing all sorts of grief, right?
What is the best way to handle this situation?
Shaun
Actually, the export tool addresses this issue. When you export a Sequence Item, the "value" property is not exported.
Instead, the "initial_value" property is exported.
<AML> <Item type="Sequence" id="EEA2CC3F0D1D47E899257601C07507D1" action="add"> <initial_value>1318</initial_value> <name>Project Number</name> </Item></AML>
When imported, the initial value will be set as the value if there the value is NULL.
This prevents resetting the Sequence accidentally.