I'm a new TRIRIGA admin and have a question that may be easy to answer for someone with more experience.  The business user asked me to apply several changes to the Space Class Current classification, which I did in a development environment.  The user has confirmed these changes are correct, and now wants them applied to our production environment.  Since it took me several hours to manually apply these changes to the Space Class Current classification within development, I'd like to use object migration to move them over to production.  My training taught me I should always include any dependencies with an object migration.  But there are about 50 dependencies listed with the Space Class Current classification in our development environment, and I don't want to migrate them all to production because I do not trust them mirroring our production environment.  Is there any particular risk to me just exporting the Space Class Current classification in dev without including dependencies, and importing it into production without performing the validation check?  This is knowing that the Space Class Current classification in dev is exactly what the customer wants to have applied to production.

------------------------------
Mike A
------------------------------

#AssetandFacilitiesManagement
#TRIRIGA

So here's a status update on my issue.  I see now my question regarding dependencies might have confused the experienced admins, but that is because I was looking in the "Business Object" area for the Space Class Current classification instead of the "Record Data" area.  And the dependencies listed for the business object did not really mean anything to me.  When I found the classification listed in with Record Data, I saw the dependencies included all the subclasses I had configured for Space Class Current.  So naturally I included all that information with the object migration, and I was able to perform the data migration successfully from one TRIRIGA environment to another.

------------------------------
Mike Aleski
------------------------------

Original Message:
Sent: Tue November 17, 2020 02:42 PM
From: Mike Aleski
Subject: question regarding object migration

I'm a new TRIRIGA admin and have a question that may be easy to answer for someone with more experience.  The business user asked me to apply several changes to the Space Class Current classification, which I did in a development environment.  The user has confirmed these changes are correct, and now wants them applied to our production environment.  Since it took me several hours to manually apply these changes to the Space Class Current classification within development, I'd like to use object migration to move them over to production.  My training taught me I should always include any dependencies with an object migration.  But there are about 50 dependencies listed with the Space Class Current classification in our development environment, and I don't want to migrate them all to production because I do not trust them mirroring our production environment.  Is there any particular risk to me just exporting the Space Class Current classification in dev without including dependencies, and importing it into production without performing the validation check?  This is knowing that the Space Class Current classification in dev is exactly what the customer wants to have applied to production.

------------------------------
Mike A
------------------------------

#AssetandFacilitiesManagement
#TRIRIGA

Mike I am glad that you solved your migration issue. I have let Ray Tripamer know.

------------------------------
David Kirwan
------------------------------

Original Message:
Sent: Wed December 09, 2020 04:17 PM
From: Mike Aleski
Subject: question regarding object migration

So here's a status update on my issue.  I see now my question regarding dependencies might have confused the experienced admins, but that is because I was looking in the "Business Object" area for the Space Class Current classification instead of the "Record Data" area.  And the dependencies listed for the business object did not really mean anything to me.  When I found the classification listed in with Record Data, I saw the dependencies included all the subclasses I had configured for Space Class Current.  So naturally I included all that information with the object migration, and I was able to perform the data migration successfully from one TRIRIGA environment to another.

------------------------------
Mike Aleski

Original Message:
Sent: Tue November 17, 2020 02:42 PM
From: Mike Aleski
Subject: question regarding object migration

I'm a new TRIRIGA admin and have a question that may be easy to answer for someone with more experience.  The business user asked me to apply several changes to the Space Class Current classification, which I did in a development environment.  The user has confirmed these changes are correct, and now wants them applied to our production environment.  Since it took me several hours to manually apply these changes to the Space Class Current classification within development, I'd like to use object migration to move them over to production.  My training taught me I should always include any dependencies with an object migration.  But there are about 50 dependencies listed with the Space Class Current classification in our development environment, and I don't want to migrate them all to production because I do not trust them mirroring our production environment.  Is there any particular risk to me just exporting the Space Class Current classification in dev without including dependencies, and importing it into production without performing the validation check?  This is knowing that the Space Class Current classification in dev is exactly what the customer wants to have applied to production.

------------------------------
Mike A
------------------------------

#AssetandFacilitiesManagement
#TRIRIGA