How to create a custom Service Request Area and get meaningful values of that in Excel reports (part 2)
In the first post I described a situation with custom enumerators and outriggers in Microsoft System Center 2012 Service Manager. This situation is common for all currently existing versions of the application.
After many tests I have found a way to resolve this issue.
DISCLAIMER: It works for me but I have to warn you that it’s “AS IS” solution and you shouldn’t do it without a full backup of your SCSM environment. In addition, I highly recommend you to practice in the lab before using in the production. You are warned and we may continue.
If you have already imported management packs with outriggers, this workaround does not work.
---------------------------------------------------------------------
Update.
Please vote on MS connect to fix this bug
https://connect.microsoft.com/WindowsServer/feedback/details/1752469
---------------------------------------------------------------------
To present values of the new custom enumerators in the OLAP cubes you have to do the following steps:
1. Delete the management packs (very carefully): Service Manager Service Catalog Cube Library, Service Manager Service Request Data Warehouse Library.
2. Open SQL Management Studio, connect to Analysis Services. There first delete Service Manager Service Catalog Library Cube, then delete ServiceRequestDim dimention.
Open SQL Management Studio, connect to Database Engine. There delete table ServiceRequestDim (All data will be lost)
3. Import the management packs: Navus.ServiceRequestAreaCustom.Library.mp, NAVUS.ServiceRequest.FormAddon.mp, Navus.customSRarea.outrigger.MP.mp, Navus.ServiceRequestAreaCustom.Extension.xml.
4. Run MPSyncJob. Wait for completion.
5. Create at least one Service Request with defined value for the new custom enumerator.
6. Import the management pack ServiceRequestWarehouseMP.mpb from the folder “C:\Program Files\Microsoft System Center 2012\Service Manager” (for R2 “C:\Program Files\Microsoft System Center 2012 R2\Service Manager”).
7. Run MPSyncJob. Wait for completion.
8. After MPSyncJob is completed, two columns, ServiceRequestAreaCustom_ServiceRequestAreaEditableId and ServiceRequestAreaCustom, will appear in the ServiceRequestDim table of the DWDataMart database.
9. Import the management pack ServiceCatalogCubes.mpb from the folder “C:\Program Files\Microsoft System Center 2012\Service Manager” (for R2 “C:\Program Files\Microsoft System Center 2012 R2\Service Manager”).
10. Run MPSyncJob. Wait for completion.
11. Wait up to 24 hours to let ETL jobs run several times and the Service Manager Service Catalog Library Cube be processed.
After this procedure you will be able to see meaningful values instead of GUIDs in Excel reports.
- Tags: OLAP Cube SCSM 2012 SCSM CUBE GUID SCSM outrigger SCSM outrigger GUID SCSM report SCUtils System Center 2012 Service Manager
Comments (8)
Greg
reply
Marat Kuanyshev
reply
Greg
reply
husmen
Or you may publish it.
Thanks
reply
Adam
I performed your instructions using my own set of management packs which perform the same ServiceRequestArea extension.
I got the same results as you up until step 8. In the ServiceRequestDim table, my custom attribute exists, but the second similarly named attribute appended with "_ServiceRequestAreaEditableId" does not appear.
Any ideas what I might have done wrong? I have compared our xml side by side and mine *should* work properly too.
Thanks
Adam
reply
Greg
reply
Wojciech Bakowski
reply
Wojciech Bakowski
Maybe your management packs extensions have already been imported into SCSM, before you start to execute instructions.
reply