Has anyone else noticed inconsistencies when re-promoting views to the Analyst Portal?

Martyn_Fearn

I have a number of views that have been promoted to the Analyst Portal.  I recently decided to add an addition column to some of these views.  When I then re-promoted the amended views I was asked if I wanted to update the existing view.  After answering Yes to this I noticed that some of the views had correctly updated and some hadn't.

I have found the only way to resolve this is to completely delete all trace of the view (from the console and portal) and re-create it from scratch.

Just wondering if anyone else has come across this and found a less drastic solution.

merlenette_jones

Martyn_Fearn said:

I have a number of views that have been promoted to the Analyst Portal.  I recently decided to add an addition column to some of these views.  When I then re-promoted the amended views I was asked if I wanted to update the existing view.  After answering Yes to this I noticed that some of the views had correctly updated and some hadn't.

I have found the only way to resolve this is to completely delete all trace of the view (from the console and portal) and re-create it from scratch.

Just wondering if anyone else has come across this and found a less drastic solution.

Hello Martyn,

I have seen this before. I usually recommend what you just did as a resolution. The reason for this is that promoted views are pulled directly from the SCSM SDK and this process at times can be a bit finicky, therefore you will have some data that does not render properly as it should. 

Let me know if you have further questions,

Merle

merlenette_jones

Martyn_Fearn said:

I have a number of views that have been promoted to the Analyst Portal.  I recently decided to add an addition column to some of these views.  When I then re-promoted the amended views I was asked if I wanted to update the existing view.  After answering Yes to this I noticed that some of the views had correctly updated and some hadn't.

I have found the only way to resolve this is to completely delete all trace of the view (from the console and portal) and re-create it from scratch.

Just wondering if anyone else has come across this and found a less drastic solution.

Hello Martyn,

I have seen this before. I usually recommend what you just did as a resolution. The reason for this is that promoted views are pulled directly from the SCSM SDK and this process at times can be a bit finicky, therefore you will have some data that does not render properly as it should. 

Let me know if you have further questions,

Merle

Steffen_Dobritz

Hi.

Is there a progress about re-promoting views for cireson portal? It takes an effort always to delete and create a view again or change the ID of the view via xml.