Hi,
used configuration:
Problem description:
XFM project with features in DGN files and linked data (good old mslink) stored in SQL Server. There are plenty of lookup tables used (not sure whether it's correct term), e.g. in feature table there is "Supplier ID" column and there is a separate table referenced with list of all suppliers with unique IDs and their names.
In Bentley Map these information are displayed correctly, so the supplier is displayed using its name. But when the project is published to i-model, it seems only data from feature table are published and lookup tables are ignored, so substantial part of data become unreadable as "human readable format" is replaced by plenty of IDs.
Is there any configuration or it's Mobile Publisher feature?
With regards,
Jan
Greetings Jan,
In Bentley Map, when using the ANALYZE FEATURE command are the supplier names displayed as expected? Does the Data Browser application also display the names instead of the ID values? If answers to both are yes, then it sounds as if you are using a Bentley Geospatial Administrator schema that defines a SQL SELECT statement that joins one table with one or more domain/lookup list tables. Is this correct?
The Bentley Map Mobile Publisher by design should be obtaining business property values for XFM feature instances with the same methods used by ANALYZE FEATURE command and the Data Browser application. However from your description it sounds as if there may be a problem. If so, we would request that you file a Service Request so that we can log an issue for further investigation.
Regards,
Jeff Bielefeld [Bentley]
Hi Jeff,
thanks for quick answer.
I am quite sure the data are displayed correctly in analyze feature tool. Later today I will try to check it and will provide more details.
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Jan,
I just performed a simple test with a feature class that uses a SQL defined "Domain List" as follows...
...and the domain/lookup value (not the ID) was published and appeared in Bentley Map Mobile as expected. In Bentley Map, the domain/lookup value also appeared in ANALYZE FEATURE command and Data Browser application.
My colleague, Inga Morozoff was able to replicate the behavior you described, noting that you were using MSLINK based business properties which I had not used in my brief test. Further investigation is continuing at this time and appropriate defect(s) will be filed. I would suggest filing a Service Request for this issue so that once the applicable fix(es) are made available you will be notified.
thanks for your update.
When any cooperation will be needed, by you or Inga , please let me know. Customer's data cannot be shared, but I guess I would be able to separate and anonimize some example.
I am curious whether some solution will be investigated, because as you can imagine, with IDs only, searching in Bentley Map Mobile is nearly impossible.
Inga has produced a test case which replicates the described behavior so no customer data should be required. Although not yet confirmed, the cause of the issue appears to be in Bentley Map and not Bentley Map Mobile Publisher. Please file the requested Service Request so related fix(es) and product update(s) can be prioritized and managed appropriately.
Hi Jeff and Inga,
thanks a lot for your effort!
Because it's in V8i and moreover probably in Bentley Map, so I assume there is a low chance there will be updated version released (comparing with a priority of BM CE development).
So now it's a race what will happen sooner ;-)
We've confirmed the reported issue requires a fix in Bentley Map and that the Data Browser exhibits the same behavior (e.g. not showing the domain/lookup value). You're correct, our priority is Bentley Map CONNECT Edition development, and Update 1 being released soon, will include MSLINK-ed project support. A new Bentley Map Mobile Publisher update is being released later this year that will include Bentley Map CONNECT Edition support as well.
Since the reported behavior does not occur when SQL Server persistency is used, you may determine data migration is the most immediate solution.
For information, I created service ticket #7000807755 for this issue and asked to link the defect with my account.