Hi,
Thanks for your suggestions.
For initial load of the data, I accept it would be possible to use the AST
forms and forget about normalization and reconciliation of the data before it
hits the golden dataset and load everything straight to it.
However, ongoing maintenance through regular
Try using the ast:computersystem form, which will feed the
bmc_computersystem and ast:attributes. This worked for me.
On Nov 2, 2015 11:43 AM, "Jarl Grøneng" wrote:
> **
> Hi
>
> You should load your attributes using the form AST:LoadAttributes, using
> the AROutput step.
You have do the import to the Join form and let the Remedy workflow to store it
in the proper table.
-Original Message-
From: Pospi ARSList
To: arslist
Sent: Mon, Nov 2, 2015 7:11 am
Subject: Loading of Asset Lifecycle Status and other
Hi
You should load your attributes using the form AST:LoadAttributes, using
the AROutput step.
Regards,
Jarl
2015-11-02 12:47 GMT+01:00 Pospi ARSList :
> **
>
> Hi all,
>
>
>
> Hope somebody can shed some light on this.
>
>
>
> As of version 8.x, all asset attributes
Hi all,
Hope somebody can shed some light on this.
As of version 8.x, all asset attributes such as Asset Lifecycle Status have
been removed from the core CMDB data model and are stored in its own asset form
called AST:Attributes.
I am trying to define a data load job to CMDB using
5 matches
Mail list logo