Skip to content
English
Submit a Support Ticket
Go To Kinexio Website
  • There are no suggestions because the search field is empty.

Oct 2026: Lease Intelligence - Store-level mobile reports are easier to manage at scale

Store-specific reporting can now be delivered more efficiently without administrators having to maintain a separate report configuration for every individual store. A shared report can use the relevant store context automatically, helping larger properties scale reporting while keeping each store's information appropriately separated.

What it is and why it matters for Lease Intelligence

Mobile Power BI reporting has been improved to make store-level reporting easier to configure and manage.

Previously, providing the same report to many different stores could require a separately configured Power BI URL for each store, with the relevant store identifier manually included in every link.

For a property with dozens or even hundreds of stores, that could create a significant administrative overhead and increase the chance of configuration errors.

The updated approach allows a common report configuration to use the relevant store information automatically, so the correct version of the report can be presented to each store.

This makes store-level reporting more scalable while helping ensure users only see information relevant to their own store.

When to use this

This approach is useful when you have a Power BI report that should be made available across multiple stores but where the information displayed needs to be filtered for each individual store.

For example, it can be used where:

  • the same sales or performance report is offered to every store;
  • each store should only see its own results;
  • a property has a large number of stores;
  • administrators want to avoid maintaining many almost-identical report links; or
  • the underlying report structure is consistent across the property.

How it works (high-level)

A shared report configuration can be set up using a base Power BI report.

When the report is presented to a store user, Kinexio uses the appropriate store context so the report can be filtered for that store.

This removes the need to manually build and maintain individual report URLs simply to insert a different store identifier.

Access is also controlled so users cannot simply change a store identifier to view another store's reporting.

The result is one more manageable report configuration that can support multiple stores while still presenting store-specific information.

Best practice tips

  • Use a consistent report structure where multiple stores need access to the same type of information.

  • Design the underlying Power BI report with store-level filtering in mind.
  • Avoid creating separate report configurations where the only difference is the store identifier.
  • Test the report using users from more than one store before rolling it out widely.
  • Confirm that each test user sees only the information relevant to their own store.
  • When the underlying Power BI report changes, test the shared configuration again to make sure the store-level filtering still behaves as expected.