Comments
BPA already provides transaction level detail within the analytical model, allowing users to drill down to the underlying journal or voucher level transactions directly in Power BI or Excel to understand what is driving a balance.The request we commonly hear is the ability to move from that analytical insight back into the operational workflow. For example, while reviewing a transaction in BPA, opening the originating journal or voucher directly in Dynamics 365 Finance and Operations for investigation or action.Because BPA is designed as a decoupled analytical store, it does not navigate users back to Finance and Operations application screens today. However, BPA retains transactional identifiers such as voucher and journal references within the model, which creates a path to enable drill back experiences where report context can be passed back into Dynamics 365 Finance and Operations.Enabling a seamless experience to analyze a transaction in BPA and then open the related record in Finance and Operations is an area of active customer interest that we are evaluating for future extensibility across BPA data models and workstreams.
This is a very valuable and practical improvement suggestion. The current behavior, where marking becomes inconsistent after reservation changes, can easily lead to confusion and unnecessary manual corrections.Ensuring that marked transactions remain dynamically linked and automatically reflect any reservation updates would significantly enhance data integrity and user experience. It would eliminate the need for users to repeatedly remove and recreate markings, reducing both effort and the risk of errors.Additionally, this change would improve transparency in inventory tracking, as linked transactions would always display accurate and aligned reservation information. This is particularly important for maintaining reliable operational processes and audit compliance.Overall, this enhancement would make the system more intuitive, efficient, and robust in real-world usage scenarios.