If the data in the database (PostgresSQL) is stored in EPSG:28992, the data can’t be used in the M.App Enterprise BI-Wizard. If you select the dataset in the BI-Wizard the wizard start loading the dataset and never quits.
If I look in the Chrome Developertools I get the following error:
Potentially unhandled rejection [40] undefined (WARNING: non-Error used)
(anonymous) @ app.js:683
o @ app.js:683
u @ app.js:683
PS. The same datasets can be used in the Thick Client, including with workflows without problems.
I know if the information in the database is stored in EPSG:4326 or EPSG:3857 it will work. The isseu here is that all my dutch clients has there data in EPSG:28992 and won't reproject there data.
Hexagon Geospatial can't expect that all company's which like to use M.App Enterprise to reproject their data. M.App Enterprise should support EPSG:28992 data in the database directly.
I agree with you and would like to underline we don't want you to reproject your data. The platform has been built to do the job in the backend, and it does already support most of the knowns CRS (BTW you can also create your custom definition).
In this specific case the issue is in the client side component. Please consider we are investing several resources to improve the BI management stuff, for the reason that in M.App Enterprise we have direct connection to a database, which scales up the needs.
Are you able to display the dataset in the rich client?
Can you give a status update of this issue? Will this be fixed in the next version? Support of the local coordinate reference system (Rijksdriehoekstelsel) EPSG28992 is important for the M.App Enterprise users in the Netherlands.
