topic Re: Publish NWD with embedded properties using DocumentControl in Navisworks API Forum

Publish NWD with embedded properties using DocumentControl

Anonymous — Tue, 20 Oct 2015 14:24:33 GMT

Hi everyone,

I have a NWF file that contains a reference to a database (via File Options | data tools), and some elements has properties that are linked to the database.

I am trying to embed external database properties when doing a publish. It works well when I go through the UI, using File | Publish.

Since the process is very long and we have many documents to publish, I want to automate this process. I tried to use the ApplicationControl and DocumentControl classes from Control API, as seen in the examples in the API folder (api\NET\examples\Controls\PublishFile)

However, in this example, even if the “Embed Database Properties” is checked, the resulting NWD file does not contain the embedded database properties.

As side notes:

- My NWF file contains one IFC and one NWC.

- Database is accessed via Native Client 11.0 (I also tried ODBC driver, and a custom DSN)

- It does not matter if the query is scoped down to apply to a subset of elements or for all elements (ie: using a WHERE xyz = prop%(“categoryname”, “itemname”)). Database properties are just not embedded in the resulting NWD file.

Thanks for your help!

Re: Publish NWD with embedded properties using DocumentControl

xiaodong_liang — Fri, 23 Oct 2015 15:01:11 GMT

Hi,

I wanted to give it a verify, unfortunately SQL connection with Navisworks did not work at my side. I am checking. Before I get back, can I know such issue is reproducible with other data source type such as Access?

Re: Publish NWD with embedded properties using DocumentControl

alain.bolduc — Fri, 23 Oct 2015 18:18:06 GMT

I have tried using it with Access but I had no succes.

I also tried with Excel data source, but the properties are still not getting embedded in the NWD file.

(please note, I am the one at my workplace that had this trouble, but another user here posted the original comment.)

I made a video showing my steps (using an Excel data source), if you want to take a look to it;

Thanks,

Alain

Re: Publish NWD with embedded properties using DocumentControl

xiaodong_liang — Mon, 26 Oct 2015 03:47:56 GMT

Hi,

Thank you for the further information! I can also reproduce this problem by the sample gatehouse.nwd and gatehouse.xls. From my test, the publishing by UI will take time if embedding database, while it is very quick if publishing nwd by API. It looks API does nothing with exporting embedding database.

I have to log this issue with our engineer team: NW DID-52394

Re: Publish NWD with embedded properties using DocumentControl

Anonymous — Thu, 06 Apr 2017 23:18:36 GMT

Was this ever fixed? Is it possible to embed database properties with the api?

Re: Publish NWD with embedded properties using DocumentControl

xiaodong_liang — Mon, 10 Apr 2017 04:40:52 GMT

Hi,

sorry, there is not an update with this issue. Since it is logged against release 2016, I will test with release 2018 to see if it works now.

Re: Publish NWD with embedded properties using DocumentControl

xiaodong_liang — Fri, 14 Apr 2017 04:14:39 GMT

Firstly, to clarify: this issue with the original post is about the problem when using Publish API in DocumentControl. Publish API works well with database if in a plugin. I tried to test wit release 2018, but hit another problem (.NET control application cannot start). So I am checking with engineer team.

At this moment, you might have to publish the document by plugin way (you could write an automation and run the plugin).

Sorry for the inconvenience.,

Re: Publish NWD with embedded properties using DocumentControl

jacob_1985 — Tue, 24 Oct 2017 08:45:50 GMT

Has this been fixed yet? I'm stuck at the exact same problem as OP. Tried both with 2016 and 2017.

Re: Publish NWD with embedded properties using DocumentControl

OR_AND_NO — Fri, 03 Nov 2017 21:05:10 GMT

It seems this problem with start API links ty mine (1) and has a long story from 2017 release (2), but I not get feedback yet.

Does anyone from Autodesk answer when they are going to fix this bug?

1: https://forums.autodesk.com/t5/navisworks-api/navisworks-api-not-licensed/td-p/7496244

2: https://forums.autodesk.com/t5/navisworks-api/confusing-navisworks-api-not-licensed-error/td-p/6430673