Hello Listers,

I am doing a migration of customizations and data from a customized
HD5 install to a clean HD6 install. I am on the last leg and have
come across an obstacle with the Related Items portion. Has anyone
had experiencing migrating the data from SHR:Assocation, specifically
records they went against the old MAINASSET or ASSETCOMPONENT forms?
I imported my assets, but since I am importing into join forms...it
does not preserve the entry-id/request id mapping although I specify
it during import... which means I cannot pull the instance id to
create the relationship since I can't get a matching search by the ID1
and ID2 fields on SHR:Association. My thoughts are maybe to parse the
Item 1 and Item 2 fields to get the Asset ID out. Is there an easier
way to achieve this?

TIA,
Jon


UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org

Jon,

There should be no reason as to why you cant import data from a version 5
SHR:Association into a version 6. all the fields in version 5 seem to be in
version 6.

However you are going to have a problem with relationships. In version 6 two
instanceid fields have been added and they are used to define the
relationships. The ID 1 and ID 2 fields are no longer used.

So what you will need to do is the following.

1. ensure all data in help desk, change and asset that you want to relate
has been loaded and has been given an InstanceID value.

2. build a filter which on merge will look up the instanceid value on the
appropriate form using the entryid specified in the ID1/2 fields and
populates the new fields.

With a bit of luck your relationships should be built.

Brian Bishop

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Jon Chau
Sent: 22 March 2006 14:11
To: arslist@ARSLIST.ORG
Subject: HD6 SHR:Association Migration from HD5

Hello Listers,

I am doing a migration of customizations and data from a customized
HD5 install to a clean HD6 install. I am on the last leg and have
come across an obstacle with the Related Items portion. Has anyone
had experiencing migrating the data from SHR:Assocation, specifically
records they went against the old MAINASSET or ASSETCOMPONENT forms?
I imported my assets, but since I am importing into join forms...it
does not preserve the entry-id/request id mapping although I specify
it during import... which means I cannot pull the instance id to
create the relationship since I can't get a matching search by the ID1
and ID2 fields on SHR:Association. My thoughts are maybe to parse the
Item 1 and Item 2 fields to get the Asset ID out. Is there an easier
way to achieve this?

TIA,
Jon



UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org


UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org

Brian,

Thanks for your response. I did know that is how I had to build the
relationships using the instance ID's which I also attempted by the
method you described. The problem is that when I imported the asset
data, the entryid/requestid which is also supposed to be the id1/2
fields on the association form do not import properly...they do not
stay the same as was specified from the source. I checked to make
sure the import tool had those fields mapped and that it handled the
duplicate id's properly by not generating a new id for each request.

Jon


UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org

Hi Jon,

Sorry for getting back to you, I have been rather busy.

If I understand you correctly your import load isn't mapping the contents of
fields id1 and id2, from your old system, to your new system. I cannot offer
any explanation for this. If you have done the mapping correctly it should
put the data in the fields.

If I have mis-understood do let me know.

Brian Bishop


-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Jon Chau
Sent: 22 March 2006 18:30
To: arslist@ARSLIST.ORG
Subject: Re: HD6 SHR:Association Migration from HD5

Brian,

Thanks for your response. I did know that is how I had to build the
relationships using the instance ID's which I also attempted by the
method you described. The problem is that when I imported the asset
data, the entryid/requestid which is also supposed to be the id1/2
fields on the association form do not import properly...they do not
stay the same as was specified from the source. I checked to make
sure the import tool had those fields mapped and that it handled the
duplicate id's properly by not generating a new id for each request.

Jon



UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org


UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org

Hi Brian,

It's okay. My import of SHR:Association is mapping the contents of
fields id1 and id2. But, when I imported the assets
(BMCBMCComputerSystem from AST:Asset), the entry ID's/request ID's
did not port over properly so I couldn't do a look up against the
BMC:BMC* forms to get the instance ID. I worked around this by
parsing out the AssetID out of the item1 and item2 fields using the
predefined Remedy functions in a filter.

Thanks,
Jon

On 3/24/06, brian.bishop@goldstag.demon.co.uk
wrote:
> Hi Jon,
>
> Sorry for getting back to you, I have been rather busy.
>
> If I understand you correctly your import load isn't mapping the contents of
> fields id1 and id2, from your old system, to your new system. I cannot offer
> any explanation for this. If you have done the mapping correctly it should
> put the data in the fields.
>
> If I have mis-understood do let me know.
>
> Brian Bishop
>
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
> [mailto:arslist@ARSLIST.ORG] On Behalf Of Jon Chau
> Sent: 22 March 2006 18:30
> To: arslist@ARSLIST.ORG
> Subject: Re: HD6 SHR:Association Migration from HD5
>
> Brian,
>
> Thanks for your response. I did know that is how I had to build the
> relationships using the instance ID's which I also attempted by the
> method you described. The problem is that when I imported the asset
> data, the entryid/requestid which is also supposed to be the id1/2
> fields on the association form do not import properly...they do not
> stay the same as was specified from the source. I checked to make
> sure the import tool had those fields mapped and that it handled the
> duplicate id's properly by not generating a new id for each request.
>
> Jon


UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org