Hi William.
I was laughing when I saw this behavior in Best Practice View a whille back. We
do have bounch different datasets for data from different sources where it gets
reconcieled in to "gold" dataset and I had same issue. It looks like they just
forgat to validate users defauilt dataset, they do set global field with it but
never check for it.
I just had to modify Active Link
HPD:INC:ViewHPDCI_100_Open
adding in to Qualification of Action two (Open Vindow) adding:
AND ('Data Set Id' = $zTmpGlobalDataSetID$)
so the Qualification looks like:
Hope this helps
('Reconciliation Identity' = $HPD_CI_ReconID$) AND ('Data Set Id' =
$zTmpGlobalDataSetID$)
________________________________
From: William Rentfrow <wrentf...@stratacominc.com>
To: arslist@ARSLIST.ORG
Sent: Thu, May 5, 2011 8:52:10 AM
Subject: Restrict dataset permissions
**
This is CMDB 7.6.03 –
Is there an easy way to restrict a staging dataset used to import/reconcile
data
to the BMC.Asset dataset so users do not see it?
We have discovered a number of instances where workflow will randomly grab the
“first matching” asset in BMC.CORE.ComputerSystem (and other classes) without
regard to evaluating which dataset it came from.
If we do this we still want the data available to all users when it goes to the
“gold” dataset.
We could just purge the data but purging out the staging data results in
problems later on. For example, if we have an asset in the staging dataset it
gets a recon ID. Apparently this recon ID is used to associate some things
(e.g., Business Services to assets) and purging the data and re-importing it
later breaks this.
William Rentfrow
Principal Consultant, StrataCom
www.stratacominc.com
715-410-8056 (C)
Personal Blog: www.williamrentfrow.com
_attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
