When the PDL updates are shipped, the data gets loaded into staging
forms initially (PDL:ESID:xxx) and from there is pushed to the forms
that are actually leveraged by the ITSM suite. There is logic on the
staging forms to create relationships and other necessary stuff. If you
were willing to go through the exercise of cleaning your data and
flagging entries in a way that says they're unwanted - possibly in the
staging forms themselves (allowing you to full on delete the entries
from the Product/Manufacturer etc. forms) - then you could hack into the
workflow logic on the staging forms and intercept the updates for those
entries - so with each new update to the PDL all your unwanteds would
not come back.
Doesn't really get you around the idea of having to plow through the
list and identify the junkie ones.
Colleen Eilbert
Effective Technologies, LLC
Chris Rom wrote:
Michael,
I am in the same boat as you and I am sure many other people are as well.
BMC boasts of 10,000+ entries in the DSL which is marketing. As you have
noticed many of the entries are pretty useless as they are freeware,
shareware or outdated (DOS, Win95, Win98) applications.
One option may be to clean up the Product Dictionary once and then maintain
it manually from there but this is labor intensive and may introduce errors.
If someone can come up with a way to 'filter' the entries on import, let me
know.
Another caveat when importing/updating the DSL Product Dictionary.
The status of the Geography_Country records is reset to the 'factory
default'.
Our company operates in over 100 countries and I had to enable many
countries since they were set to 'Offline' in the initial install.
A look at the cdf_data.xml file from 'DSL7DataPatch1518_v109_05_0_1'
confirms this:
<df Mode="update"
altfid="301678500">PDL_ESIDsuites109_05_0_1_cfg.arx</df>
<df Mode="update"
altfid="4">PDL_ESIDsuiteapps109_05_0_1_cfg.arx</df>
<df Mode="update"
altfid="301677200">PDL_ESIDapps109_05_0_1_cfg.arx</df>
<df Mode="update"
altfid="301677400">PDL_ESIDfiles109_05_0_1_cfg.arx</df>
<df Mode="update" altfid="4">PDL_ESIDappfiles109_05_0_1_cfg.arx</df>
<df Mode="update"
altfid="301678900">PDL_ESIDmanufacturer109_05_0_1_cfg.arx</df>
<df Mode="update"
altfid="400014400">PDL_ESIDversioninfo109_05_0_1_cfg.arx</df>
<df Mode="replace">CFG_GeographyCountry109_05_0_1_cfg.arx</df>
</Data_File_List>
I have opened a support case with BMC Remedy Support.
Rgds,
Chris Rom
Schlumberger
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers
Are"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers
Are"
