2023 R2: Workaround for the ShowContent() symbols not disappearing on context change anymore

Hello Quentin, 
My immediate ideas

1) Maintain the list of content names and their panes (which can be challenge with Autofill algorithms)
2) Would be to add a custom property to symbols being display by ShowContent  (e.g. HideOnContextChange with default false) 
Then on the same symbol have a datachange script something like that:

Expression: MyViewApp.Navigation.Current
Body:

if HideOnContextChange then
HideSelf();
endif;

Now where you use the ShowContent() you can pass a custom property value to it (below is the additional lines to add 

Dim cpValues [1] as aaContent.PropertyOverrideValue;
cpValues[1] = new aaContent.PropertyOverrideValue("HideOnContextChange", "True", true);
contentInfo.PropertyOverrideValues = cpValues;

The complete example you can see in the online help for ShowContent()

Thanks a lot, we'll look into that second idea, seems like a reliable way of doing it

I implemented that idea on a test symbol and found one issue: the datachange script runs when the symbol opens (I guess nothing => current context is technically a data change) which hides the symbol instantly.

To counter that, I've added another custom property ContextOnOpening to the symbol
It's then filled by the "On Opening" script with a simple

ContextOnOpening = MyViewApp.Navigation.Current;

And the datachange script has been modified so that the HideSelf isnt ran if the current context is identical to the context on opening the symbol

if HideOnContextChange and  MyViewApp.Navigation.Current <> ContextOnOpening then
HideSelf();
endif;

So far it's working perfectly, we'll keep testing but that seems to be the way we'll go when we migrate the production galaxy to 2023 R2

Thats great, you could have probaby handle it with
if HideOnContextChange AND MyViewApp.Navigation.Current<>"" then
HideSelf();
endif;

I did try that but it wouldnt work, according to the customlog by the time the script runs through the IF condition, MyViewApp.Navigation.Current is already filled in with the context name

Hi Quentin, I just wanted to let you know I am following with our team as to why we made the original changed that effected your application. I would have not expected that. I'll keep you posted with my analysis results.

Hi Quentine,

I followed with our team on this issue and this issue is a BUG and will be fixed in SP2023R2P01 that is currently planned to be released mid-June 2024. Hence, I would recommend you hold on with modifying your application.

IMS Request 3060445: Pane with multi content and autofill does not works the same way in 2020 R2 and 2023 R2 version.

Sorry for the inconvenient that it made to you and sorry for the incorrect respond you initially got.

Hi

It's very annoying when changes are made like this.
You can encapsulate the hide line with an empty try catch:

dim contentInfo as aaContent.ContentInfo;
contentInfo.PaneName = "NameOfThePane";
contentInfo.ContentType = "App_Device_Faceplate";
try
   HideContent(contentInfo);
catch
endtry;

Occassionally we make some changes to improve performance characteristics of OMI - in this case it broke an exisiting experience which we deem to be a regression (something worked and does not anymore).  The issue should be fixed in the upcoming Patch 01 (targeted for early July).

It did make me wonder if this should not be something optional - in some cases, I might want the manually shown content to stick around after changing context... Or will that never be the case? I do agree that by default it should disappear, I was just wondering if anyone has a use case for making it stay put...