Custom Type Projection Not Saving Changes When Saving New Incident

Adrian_Paech

We have a requirement to have a "Preferred Contact User" UserPicker field associated to our incidents.
I followed cireson KB article:
https://support.cireson.com/KnowledgeBase/View/1174#/

I managed to get the new Type Projection working, imported into SCSM, added the Type Projection GUID into the Admin settings, and updated Incident.js to show the new "PreferredContactUser" field.

When opening an "existing" incident in the portal, I can save the Preferred Contact User, and it sticks.
However, when logging a "new" incident, the Preferred Contact User information is not sticking.

I have attached a zip file with my Type Projection.

One includes console form customisations (so you can test it in the console and portal).
The other is clean, and does not include any console form customisations (so you can only test in the portal).

I have already logged an incident for this (https://support.cireson.com/Incident/Edit/IR49081/)
But any help from the community would also be appreciated

Kind Regards,
Adrian

carrie_medine

Hello Adrian,
When creating the new Incident the template that is used must be based on a type projection that contains your extension.    Within SCSM you must make sure that any templates are "touched" after you have made your extension to the incident class.  By "touched" I mean you should open the template within the console and re-save it.    If you are just clicking New Incident that is using whatever template you have specified in the Admin->SettingsItem called "DefaultIncidentTemplate".

After making these changes - it is best to Restart the Portal website and Re-cycle the application pool so its working from fresh data.

As a side note - this behavior is an odd quirk within SCSM that seems to happen when you extend a class after you have already created templates.

Thanks,
Carrie

carrie_medine

Hello Adrian,
When creating the new Incident the template that is used must be based on a type projection that contains your extension.    Within SCSM you must make sure that any templates are "touched" after you have made your extension to the incident class.  By "touched" I mean you should open the template within the console and re-save it.    If you are just clicking New Incident that is using whatever template you have specified in the Admin->SettingsItem called "DefaultIncidentTemplate".

After making these changes - it is best to Restart the Portal website and Re-cycle the application pool so its working from fresh data.

As a side note - this behavior is an odd quirk within SCSM that seems to happen when you extend a class after you have already created templates.

Thanks,
Carrie

Adrian_Paech

Thanks Carrie.. Just about try and attempt this today. Will let you know how I go..

Adrian_Paech

That fixed it! Thanks Carrie

Regards, Adrian

Dieter_Saerens

I have the same problem with a relation and type projection between Location and User. I mapped the form with the right ID to an AD Group, but it doesn't load the new form I added to the Location.JS.

Any suggestions?

john_doyle

Hi @Dieter_Saerens 

I should have read this comment before I replied in the other thread. In the current release, the type projection used by the Location form is hard-coded into the form controller and cannot be changed. The form will not load any related objects which are not included in that type projection.