#SAP LUMIRA DESIGNER DIVISION VARIABLE UPDATE#
#SAP LUMIRA DESIGNER DIVISION VARIABLE PATCH#
#SAP LUMIRA DESIGNER DIVISION VARIABLE CODE#

Solution: 2840323 - Report-Report-Interface (RRI) does not work with Lumira 2.3 In the source application you have to add these additional URL parameters as well with the correct values.

#SAP LUMIRA DESIGNER DIVISION VARIABLE CODE#

Possible workaround: change the target application to use proprietary URL parameters (global variable) and then use code in OnStartup to set the filter based on these parameters.

when starting an RRI target with a filter parameter, this filter will not be applied. Note 2668995 - Unpredictable Behavior of Lumira 2.1 Apps with enabled Undo/Redo Background Processing => Data source not loadedДЄs of Lumira 2.3 RRI filter parameter are ignored in the target application, i.e. You have to change the steps value to 0В instead of e.g.

open your application in the Designer and go to the property sheet of the application:.

You have to disable the usage of undo/redo in all applications that use background processing. Total time: 4837 ms, Lumira Designer time: 326 ms, data sources time: 4511 msД¤730 ms: Process request: Application startupД¤403 ms (1 ms not covered): Prepare ProcessingДЈ354 ms (924 ms not covered): Set Page State (Data Providers)ДЎ83 ms: Synchronize State Variables (in parallel via processing groups)ДЁ8 ms (2 ms not covered): Destroy data provider DS_XYZДҐ1 ms: RFC BICS_PROV_CLOSE

The easiest way to detect the problem is to check the prolfiling trace for the ' Set Page State' and for the destruction of data provider / data sources ( RFC BICS_PROV_CLOSE) which were loaded before

#SAP LUMIRA DESIGNER DIVISION VARIABLE UPDATE#

It only occurs if Undo / Redo steps are greater than 0.ДЄs of our analysis this occurs when charts are shown during background processing and charts fire Update Properties HTTP requests to the server before the next background processing step. This leads to errors like 'Data source not loaded' in UI elemenets like charts or cross tab. Symptom: During background processing steps data sources loaded before can be unloaded again.

#SAP LUMIRA DESIGNER DIVISION VARIABLE PATCH#

In Lumira 2.1 until 2.1 SP 1 Patch 1 there is a know issue which has the following side effect:

Mysterious Memberlists in Lumira DesignerДynamic Apps in Lumira 2.1 вЂ“ Iterating Over a ResultsetД«ackground Processing => Data source not loaded Inside the the OnXXX methods all API calls are checked in detail whether they are allowed or not.ДЇIX: You have to move the code from your global functions to the OnXXX functions and execute them directly there. The reason why we need to prevent these kind of calls is that they could lead to dramatic errors when they call the wrong API like endless loops or dumps. The Designer always showed an error message 'Couldn't resolve reference to Member '.'' also in previous versions: This was an error in previous versions of Lumira that these functions were executed during runtime. Global Functions are not callable from On Before Prompts Submit, On Variable InitializationДЄs of Lumira Designer 2.3 global functions are not called anymore.

Sap lumira designer division variable