Error after Selecting Location

Margarete_Jussen · October 2018

Hello, we have a configsometimes the chosen asset location is displayed with a red Background meaning no location is chosen. Unfortunately I cannot ad a screenshot here because I am getting an error message. I hope you will understand my problem nevertheless. While testing I recognized that the problem occurs after deleting a selected location and then while choosing a location the second time after deleting. This occurs in each browser type. (Chrome, Edge, IE and Firefox)

Our Support complains about this that this would make their Hotline support worse.

Could anyone help please.

Regards Margret

Brian_Wiest · October 2018

If you are deleting an object from the configuration but it is still showing up on the portal, that is due to the IIS App pool. Recycle the pool after deleting and the option will not be available to chose from.

Margarete_Jussen · October 2018

Thanks for your answer. Iam sorry I did not eyplain the problem correctly. We delete it just in the input field of the drop down menu and select a new one twice until the error occurs. That is what I must do to reproduce the complained error of our support engeneers.

Brian_Wiest · October 2018

Ok so it sounds like you have a custom enum for your locations. Then you have a custom JS to make it red if an object is not chosen.

Then if an analyst chooses a location, backspaces to remove the option from the list, selects another location. Then selects that same location again, an error appears on the portal.

If that is a correct run thru, you should check the observer of the Red formatting to see if it is updating on change. Monitor dev tools in the browser see what it reports when you replicate the error.

Another option is to turn off all your customspace objects and see if the error clears, then turn on one at a time until you replicate the error so you know when customspace object is causing the error. HTH

Margarete_Jussen · October 2018

I renamed my custom directory but the error stays. We have this problem since SCSM 2016. I now recognized that the red formatting also occurs if I click next (right) to the displayed chosen location.

Brian_Wiest · October 2018

Ok so it sounds like you are in a ARO with you have a required query lookup for CI Type location?

If true is this a CI from Cireson Asset Management, or a custom CI?

Also reading between the lines you migrated/upgraded from SCSM 2012 to 2016. Where it worked in 2012 but now you have the error. What method did you use to get to 2016.

From my experience, we had a couple issues when we migrated. We choose to move from one server farm to a new to address lessons learned from our 2012 deployment. (had a lot of garbage to clean up)

So when upgrading we didn't want to loss all the work we did customizing the portal navigation and dashboards. So it was recommended to lift the DB into the new farm, install the latest portal and move forward. This worked but later we ran into an weird issue that CI's when chosen to add to a WI when clicking save they would disappear. We discovered the offset was that in the DB life there were CI's into the configurationitem table that we not in the new SCSM DB. Wondering if you are running into something similar.

Couple other things you can check. If it is Cireson Asset Management, verify that it is showing properly licensed. Verify the CI's are opening properly in the console. Check that they can be found in the DB on the configurationitem table, noting depending on the upgrade path they could be stale records. During off hours you can always clear that table and restart the cache builder. (that is how we cleared out our issue)

HTH

Margarete_Jussen · October 2018

We found out that we are having this problem while creating a ticket with a template using the rquest icons in portal. If I create a ticket with the same template using the "New +" in the left corner of the portal everything is fine.

Brian_Wiest · October 2018

So the community can help more please define more what the implementation is for the use case.

Request Icons - Service Requests or Navigation Node?

What class of New are you working on - Incident or Asset management?

If Incident - Location is not natively a form element how did you customize the form?

Margarete_Jussen · October 2018

Image: https://us.v-cdn.net/6026663/uploads/editor/dd/zcv23rjl195g.png

For exampel here I select "Anforderung Drucker" what is a Service Request. The green and blue icons are SRs, the orange and red ones IRs. The error occurs for IRs and SRs.

The Error looks like this:

Image: https://us.v-cdn.net/6026663/uploads/editor/sm/zt5f3k2u04pl.png

We have a customization in our servicerequest.js file in custom directory:

{

columnFieldList: [

{ DataType: "Enum", PropertyDisplayName: "Standort", PropertyName: "Standort", EnumId: '6710d24d-b9f7-dbfc-076d-076bc256f703'}

],

},

We have an enum list UKA_SM_Enum_UKAStandorte. Here an extract of this list:

<ID>UKA_SM_Enum_UKAStandorte</ID>

</Identity>

<Name>UKA_SM_Enum_UKAStandorte</Name>

<ID>Microsoft.EnterpriseManagement.ServiceManager.UI.Console</ID>

</Reference>

<ID>System.Library</ID>

</Reference>

<ID>UKAStandorteMP</ID>

</Reference>

</References>

</Manifest>

The list is much longer. We also have a language pack in this management pack. Here an extract:

</EnumerationTypes>

</EntityTypes>

</TypeDefinitions>

<ManagementPackName>UKA_SM_Enum_UKAStandorte</ManagementPackName>

</Category>

</Categories>

<Name>UKA_SM_Enum_UKAStandorte</Name>

<Description>Standorte UKA Raumbuch</Description>

</DisplayString>

</DisplayString>

</DisplayString>

</DisplayString>

<Name>UBFT Etage 01 Flur 01 / Raum 00 Flur 01 incl. Windfang A1</Name>

<Description>UBFT Etage 01 Flur 01 / Raum 00 Flur 01 incl. Windfang A1</Description>

</DisplayString>

<Name>UBFT Etage 01 Flur 01 / Raum 01 Büro Leitung</Name>

<Description>UBFT Etage 01 Flur 01 / Raum 01 Büro Leitung</Description>

</DisplayString>

<Name>UBFT Etage 01 Flur 01 / Raum 02 Sekretariat</Name>

<Description>UBFT Etage 01 Flur 01 / Raum 02 Sekretariat</Description>

</DisplayString>

<Name>UBFT Etage 01 Flur 01 / Raum 03 Büro</Name>

<Description>UBFT Etage 01 Flur 01 / Raum 03 Büro</Description>

</DisplayString>

<Name>UBFT Etage 01 Flur 01 / Raum 04 Büro</Name>

<Description>UBFT Etage 01 Flur 01 / Raum 04 Büro</Description>

</DisplayString>

<Name>UBFT Etage 01 Flur 01 / Raum 05 Büro</Name>

<Description>UBFT Etage 01 Flur 01 / Raum 05 Büro</Description>

</DisplayString>

<Name>UBFT Etage 01 Flur 01 / Raum 06 Büro</Name>

<Description>UBFT Etage 01 Flur 01 / Raum 06 Büro</Description>

</DisplayString>

<Name>UBFT Etage 01 Flur 01 / Raum 07 Kommunikationsraum</Name>

<Description>UBFT Etage 01 Flur 01 / Raum 07 Kommunikationsraum</Description>

</DisplayString>

<Name>UBFT Etage 01 Flur 01 / Raum 08 Büro</Name>

<Description>UBFT Etage 01 Flur 01 / Raum 08 Büro</Description>

</DisplayString>

<Name>UBFT Etage 01 Flur 01 / Raum 09 Küche</Name>

<Description>UBFT Etage 01 Flur 01 / Raum 09 Küche</Description>

</DisplayString>

<Name>UBFT Etage 01 Flur 01 / Raum 10 Büro</Name>

<Description>UBFT Etage 01 Flur 01 / Raum 10 Büro</Description>

</DisplayString>

<Name>UBFT Etage 01 Flur 01 / Raum 11 Behandlungsraum</Name>

<Description>UBFT Etage 01 Flur 01 / Raum 11 Behandlungsraum</Description>

</DisplayString>

<Name>UBFT Etage 01 Flur 01 / Raum 12 Kommunikationsraum</Name>

<Description>UBFT Etage 01 Flur 01 / Raum 12 Kommunikationsraum</Description>

</DisplayString>

<Name>UBFT Etage 01 Flur 01 / Raum 12a Technikraum</Name>

<Description>UBFT Etage 01 Flur 01 / Raum 12a Technikraum</Description>

</DisplayString>

<Name>UBFT Etage 01 Flur 01 / Raum 13 Lagerraum</Name>

<Description>UBFT Etage 01 Flur 01 / Raum 13 Lagerraum</Description>

</DisplayString>

</DisplayString>

<Name>UBFT Etage 01 Flur 02 / Raum 00 Flur 02</Name>

<Description>UBFT Etage 01 Flur 02 / Raum 00 Flur 02</Description>

I hope these informations will help.

Brian_Wiest · October 2018

Ok that helps,

So your Customization of the ServiceRequest.JS is correct and you have verified that it is working.

Which also means your MP's are working for the custom enum.

From the screenshots your ARO is what is running into the issue.

For your migration to 2016 was it an in-place upgrade or a migration.(If migration did you use the lifecycle app to transfer the MP's)

I would review the RO design in the console.

Verify that it is reading the input as an enum linked to your custom enum.

Verify that it is reporting properly mapping to that data point.

You may need to unpublish double check the settings and then publish again. Restart the cache so it syncs again. Possible stale content in the Cireson DB from the upgrade/migration.

HTH

Margarete_Jussen · October 2018

We did a migration and used lifecycle app. I checked the RO in console and unpublished and published afterwards.

Margarete_Jussen · October 2018

Do you have any idea what the message WARNING: Tried to load angular more than once. mean and if it could have anythin to do with our problem? THis message occurs while loading Cireson Portal

Brian_Wiest · October 2018

Did you also lift the database? Or was it a fresh Cireson install.

Margarete_Jussen · October 2018

The database was a fresh install.

Margarete_Jussen · October 2018

Thank you very much for your help. I could not find the problem so I raised a ticket at Cireson Support Portal.

Error after Selecting Location

Answers

CIRESON COMMUNITY WEB SITE