When a parameter is created with numeric range and data type decimal with maximum value 5000 and increment of 0.1 and used in a slicer, the input numbers rounds off to nearest whole number. Example: when user enters 2 in the slicer, then the input is taken as 0 and if 3 is entered then rounds to 5 which is the nearest whole number. When a parameter reaches the limit of 1000 as per document, additional values cannot be loaded, which restricts its usability in real‑world enterprise scenarios. Many organizations rely on parameters to dynamically filter large datasets, such as user lists, customer IDs, product catalogs, or report‑level security mappings. In such cases, the 1,000‑value ceiling becomes a hard blocker, forcing customers to redesign models, split reports, or abandon parameter‑based logic entirely. Increasing this limit would significantly improve scalability and reduce unnecessary complexity in report and model design..
Conclusion: Increasing the limit from 1000 to higher value is proposed to meet business requirements.
Ref doc: Use Parameters to Visualize Variables - Power BI | Microsoft Learn
Recent ideas
Support Native SQL LIKE / NOT LIKE Wildcard Filtering Across Power BI Reports
Description Currently, Power BI does not provide a native way for report consumers to perform dynamic SQL-style wildcard filtering using patterns such as LIKE '____' - Above return all values wit...Seeralan1 hour agoNew MemberNew4Views0likes0CommentsRetain Matrix/Table Scroll Position When Returning from Drillthrough
Description: Currently, when users drill through from a Matrix or Table visual to a detailed page and then use the Back button to return, the report navigates back to the source page but resets the ...Pruthviraj152 hours agoNew MemberNew13Views0likes0Comments