07-24-2020 03:32 AM
What is the version of M.App Enterprise you are using here? Is it the latest version 2019 Update 4?
Please open browser console (F12 most browsers) and monitor for any errors there during the data reading. You may also switch to the 'network' tab (re-try to load the feature) and inspect the request/response for any details.
Is your input feature coming from vector sets or some other source?
It could be that the input feature set includes some invalid geometries.
07-24-2020 04:54 AM
There is newer update 4 available at this time.
You may upgrade and test there. This would be my first recommendation.
Perhaps you may also investigate the cancelled requests from Console Log.
Are they indicating what may be going wrong with the input features?
Are you using vector set feature input data? If yes, there should be a call to the vector set made followed by a SQL Query against the specific dataset of the vector set. I am unable to discern this from your screenshot unfortunately.
09-10-2020 02:17 AM
I have just had the same issue. It was because the column names had spaces which isn't good for Postgres! Removing the spaces (e.g. Old FID -> OldFID) did the trick. Hope this helps. Johnnie