Replies: 2 comments 1 reply
-
On a side not, I attempted test the above workflow by adding a geometric element to a standalone iModel using DTA, and had the following issue:
Is this workflow currently bugged in DTA? |
Beta Was this translation helpful? Give feedback.
1 reply
-
This is what I use for testing with standalone imodels in a studio test app as well. This plus enterEditingScope should be all you need. dta place linestring currently works as well, I used it yesterday. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Context
We are currently experimenting with storing Standalone iModels in component center for users to use as "templates" when creating sheets by harnessing transformations.
We are currently having trouble with the editing workflow for users to make updates to these standalone iModels. The intent is to download the standalone iModel, edit it, then upload it as a new version of the template. The problem is that when editing the standalone, the tiles are not getting updated with the new geometric elements.
I understand it to be a tile update issues because, the geometry is not visible when inserted. If I zoom into the view more than I have previous, the tiles have the inserted geometry. If the iModel is closed, the tiles cache delete, and the iModel is opened again, the new geometry is visible.
We are using similar logic to open and edit iModels from the hub and that works, but not with standalones. To review what we are doing:
iModel = await BriefcaseConnection.openStandalone(path1, OpenMode.ReadWrite);
(obviously not using openStandalone iModels that are not standalone)await iModelConnection.enterEditingScope();
await basicManipulationIpc.insertGeometricElement(props);
It's been awhile since I set this up so it's possible I'm missing a step. If so, I apologizes
Questions
CC: @ashish-srivastava-dev
Beta Was this translation helpful? Give feedback.
All reactions