This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Is there a way to upload the primary key attribute like workorderid or assetid through MIF and not use the maximo sequence? Primary key column is a restricted column and cannot be overridden (option is readonly) to unrestrict it. Is there any way to achieve this?
Well first of all, workorderid and assetid are the "unique columns" for these objects, not the primary keys, and there is a difference in Maximo. As such they are used internally only, so my question would be why would you ever want to override and not use the sequence?
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com]
Sent: Friday, August 22, 2014 4:46 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Uploading Primary Key attribute through MIF
Is there a way to upload the primary key attribute like workorderid or assetid through MIF and not use the maximo sequence? Primary key column is a restricted column and cannot be overridden (option is readonly) to unrestrict it. Is there any way to achieve this?
we want to migrate selective data from one maximo environment to another through MIF and at the same time want the unique key value to be copied as well.
When migrating through MIF, the unique key value would be generated again which is what we want to avoid.
Why does it matter that the unique key value would be generated again? I'm not sure I understand what difference that would make.
If there is really is a need for the value in the unique column to remain the same across the two environments, you'll probably have to do this from the back end rather than using the MIF. Even if you could get the MIF to accept the values you are passing in, you'll then have to go and muck with the sequences that are used to generate those values, otherwise you'll have uniqueness issues when creating new records.
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com]
Sent: Thursday, September 04, 2014 12:48 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: Uploading Primary Key attribute through MIF
we want to migrate selective data from one maximo environment to another through MIF and at the same time want the unique key value to be copied as well.
When migrating through MIF, the unique key value would be generated again which is what we want to avoid.
Workflows and few other objects refer records using id and not their primary key. Since I need to copy record along with all its related objects including workflows, i need to maintain the id in the other database.
Since its not possible through MIC we are taking the database move approach.
Thanks.
How you gonna do that on db level, there is a lot of relationship in data dictionary, why don't you use migration manager to do the task, there you can move ur meta data from one environment to the next, in maximo there is two types of datas application data and data dictionary, auto key is the part of data dictionary , you can use mif to load ur application data.
Sent from my iPhone 5s
> On Sep 7, 2014, at 11:05 AM, "pranjal149@yahoo.com [MAXIMO]" <MAXIMO@yahoogroups.com> wrote:
>
> Workflows and few other objects refer records using id and not their primary key. Since I need to copy record along with all its related objects including workflows, i need to maintain the id in the other database.
>
> Since its not possible through MIC we are taking the database move approach.
>
>
> Thanks.
>
>
>
>