Navisworsk Datatool query with dynamic columns.
I am herewith attached image to get clear idea of my question.
I don't think so. You will likely have to build a plug-in which manages its own SQL connection and query generation. You might want to build your own property display palette, or you could have it auto-append custom property tabs to objects as they are inspected.
----------------------------------
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
Liang ,
dgorsman,
Thank for for your imputs.
Creating custom property catagory and properties for a plant will takes days/weeks to complete. Because i already implemented this solution and is not good for a big plant.
Is there any way to implement like creating linkage for modelitem? Since i can move my property data from SQL server to any other format.
My idea is, I am having my own unique key for each modelitem, that act as a linkage between model item and the data source ( may be like DRV in PDS.)
Basically i wants to implement a functionality like PDS DGN. Each Element is mapped with unique linkage value called DMRD Linkage and there is an entry for each DMRS Linkage in DRV file which acts as datasource for external attributes. So that navisworks shows the "PDS Component Data" category in Property window and displays attributs which will vary based on the selected model item.
Why i need is.
1. Creating new property category and properties is time consuming if the model is large.
2. Using plugin and own property grid approach, we can't use in freedom.
So the linkage and DRV approach is good in performance wise while publish and we can use the file in freedom with extended attribute.
Please provide me some input based on the above.
Thank you.
Populating *everything* does take a lot of time, true. But thats where you need to start cheating. Don't populate objects that aren't inspected, and save the data for those that have already been inspected. For example, with your own palette it first checks to see if the selected object(s) have the required data, if not query the database then add it to the object. Objects are populated as you go. Of course if you go with a separate palette it doesn't have to read the Navisworks properties at all it can be purely driven from database queries.
----------------------------------
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
If you want a stand-alone NWD file that functions with only Freedom, then you don't have a choice - you'll have to work with the current means even if its slow. You might try working with more smaller files, populating the addtional data, publishing those to NWD, then merging the NWD files together. That would also allow you to split the work over multiple computers for additional time savings.
----------------------------------
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.