It seems that depending parameters aren't automatically updated in Paginated Reports while in PBIRS/SSRS they do.
For example, if a paginated report has two integer based parameters called 'Century' and 'YearNo' which can be changed by the end user, and a third one called 'Year' is depending on the input of 'Century' and 'YearNo' (possible value and default value ‘Year’=’Century’ + ‘YearNo’), then parameter 'Year' isn't automatically updated if one of the depending parameters (Century, YearNo) has been changed by the end user. The end user must explicitly select the 'Year' parameter again in PBI Premium while the given parameter automatically gets updated in PBIRS/SSRS.
This issue causes additional actions to be done by the end user, but more importantly, hidden (or internal) parameters that are depending on the input of other parameters can’t be used in Paginated Reports via PBI Premium in the cloud, while in (normal) PBIRS/SSRS they can!
Screenshot PBIRS/SSRS after updating ‘YearNo’ to 19 and leaving ‘Century’ to the default setting of 2000: Year automatically gets updated to 2019
Screenshot PBI Premium after updating ‘YearNo’ to 19 and leaving ‘Century’ to the default setting of 2000: The possible value to be selected gets indeed updated. However, the end user must select the parameter again!
-
DNMAF
on:
Adding a measure or column as a tooltip to an Azur...
-
parry2k
on:
A Typo about Refence Line in the Format (Korean)
- ricardo_ona on: UDFs annotations Issue with Invoke-ProcessASDataba...
- DeeBaxo on: Export to PowerBI directly from Sharepoint List
-
mattlee
on:
Automatically expand table columns to fill availab...
- Ghoom on: Azure Maps Controls -> Selection Greyed out
-
awright19
on:
Open old report, PowerBi hangs
-
mattlee
on:
Error：Visuals display blank when export report to ...
-
mattlee
on:
New Button Slicer: Issue with the Grid type of Arr...
-
mattlee
on:
List Slicer Button Dimensions Ignored in Service