Skip to main content

A published BR report in IFS Cloud 23R1 contains 2 parameters for Date_From and Date_To. These are defaulted to #START_OF_LAST_WEEK# and #START_OF_THIS_WEEK#. Executing the report in the BR client this works as expected - the date range is rendered as expected.

 

However, ordering the published report through Info Services, these default values does not show - and are not allowed. Similarly result for Global BR Parameters. 

 

Is this how it is supposed to work in core ?

I.e. that Context Substitution Variables are not available / implemented for reports of type BR reports ordered / scheduled via Info Services.

@InfKristN We are using 23R2 and raised with support, and was advised that the use of context variables has not been implemented by R&D in Cloud despite it being there in previous versions of IFS!

No visibility if this functionality will be re-introduced in a future release unfortunately.

We had to amend the business reporter reports to have the context built into them, so when they were scheduled reports they would behave the same in terms of looking for data for this week or this month.

@SHAUN_KERSLAKE  Thank you for sharing. 

It becomes a rather blunt tool. Not sure I follow the “work around” with context built in. 

Rgds,

//Kris

@InfKristN Agree it does seem a little mad that IFS would remove key functionality in Cloud, as this is a backwards step when coming from Apps 10 for example. 

The workaround for us was that we had to amend the Business Reporter report to restrict the data based on the scheduling requirements. 

So for example in Apps 10, we have setup scheduled report with context variables #START_OF_LAST_WEEK#. This doesn’t work in Cloud, so the specific report had to have the context applied within the actual BR report. Subsequently when you come to schedule the report in Cloud, the parameter is no longer required.

Reply


Terms & ConditionsCookie settings