I have a need to access a ready-only copy of the AX business database that is sync'd in real time. We can then sync this database to our own azure sql database for reporting purposes.
Comments
Unable to vote up, but this, or some alternative is essential. We are live with D365fO for over a year and have had huge problems reporting transactional data. Eventually we got incremental export to BYOD working, but it took 9 months of pain. MSFT not allowing use of RecId as an index in data entities was the core problem.
We were unable to load the initial data (8 million records) and had to push day by day.
Now operational we find BYOD exports hurt system performance.
Its our data and our system, MSFT need to give us access to it so we can report.
Category: Reporting and Analytics
Unable to vote but I think this is essential. BYOD is feasible but not cost effective and too many unnecessary road blocks
Category: Reporting and Analytics
This feature is necessary for the following reasons
1. Validation of huge load of records
2. In case of multiple integrations points, this feature will help in identifying missing records
Note : Customer is concerned on the cost for BOYD.
Category: Reporting and Analytics
Yes, Really required for reporting purpose
Category: Reporting and Analytics
The product team plans to get some feedback on this item, can you please join our Yammer group for further discussion on this topic?
https://www.yammer.com/dynamicsaxfeedbackprograms/#/threads/inGroup?type=in_group&feedId=5302821
Category: Reporting and Analytics
The product team plans to get some feedback on this item, can you please join our Yammer group for further discussion on this topic?
https://www.yammer.com/dynamicsaxfeedbackprograms/#/threads/inGroup?type=in_group&feedId=5302821
Category: Reporting and Analytics
It is asbsolutely necessary to have access to real time read only copy of the Dynamics 365 for operations database in order to be able to continue to provide our customers with reliable, effective and affordable BI solution based on D356FO data.
Category: Reporting and Analytics
Using entity increase at least 30% time to implement an enterprise BI solution.
Please give access to secondary read-only application database.
Category: Reporting and Analytics
This is an absolutely critical feature for our company to jump from 2012 R3 to D365. The number of transactions we process combined with the reporting that is required cannot be accomplished with entities alone. Our executive team cannot and will not wait for the development cycle to get an entity created to have information available.
Category: Reporting and Analytics
Our biggest problems are the following:
- Performance/Scalability: Currently in a pre-production scenario we are exporting 5.000.000 records in round about 7 minutes. If we think of the volume after one month or even one year we will end up in a lot longer processing time. Of course we can use change tracking on transaction level, but when something goes wrong we have to re-transfer the whole thing.
- Leak of documentation: Most of the (new) features we had to reverse engineer to figure out how to use them and how they work. You mentioned the support for DB triggers. As far as I know there is no documentation how to use this feature.
- Reliability: If we have a big data project we want to export to BYOD, there is no trigger mechanism to tell the “consuming side” that the export has successfully finished and that they can start to read from the BYOD. It gets even worth if the export fails after 3 of 10 entities. Then you have a mix of new and old data.
- Costs: Our customer has the opinion that he pays for D365FO and the data inside the system is his data. So why should the customer pay again for using his own data?
Category: Reporting and Analytics
Administrator on 7/30/2019 3:41:40 PM
We are looking into adding more data into Azure Data Lake including the option to add Entities and key tables.