Data Shortcuts

[rdisacks]

Hi,

For a stormwater system pipe network that gets data shortcutted to another basefile, how do you make sure those different structure styles (manhole, curb inlet, area drain), etc. carry through to the basefile that they are being data referenced? It seems as though I always have to manually go and switch structure styles from the default that they come in as.

Thanks

[cwr-pae]

Make sure your Parts List is the same between the 2 files. Either use the same template or drag and drop it from the source file to the client file. You also have to have all the styles in both drawings. You can import from the file for styles, the parts list will not import but must be dragged and dropped. If you make changes to the styles you have to update (by drag and drop) the part list and styles (by import or d&d). For the best function d'refs you should assign styles in the parts list and by swapping parts to change styles in your source drawing. All this doesn't necessarily work 100%, but it does come close.

[brian.strandberg]

Yep - its all in the part list.  Anytime you data shortcut something you are only getting the data, not the style.  Having the same part list in both drawings, helps it get it right.  Its going to look at the part list, in my case the structures snip below, and it will use those styles. When it sees an eccentric cylindrical structure, it will look at this information for which style it will use.

[lim.wendy]

Hi Ron.

Thanks for reaching out to the forum. Have you had a chance to look over the suggestions provided by our experts?
Please let us know if you require further assistance.

If the suggestions helped you, please hit the "Accept Solution" button, as it helps make the solution easier to find for others who might have the same issue. Knowing which topics are solved or not can also help our many users find the questions that still need to be answered. It’s also a great way to say thank you and give recognition to whoever helped you. 

[cwr001]

The above mentioned methods are the way - they do however show one of many shortcomings, as far as pipe networks are concerened. I havn't found a good way around that, maybe someone can help:

In my experience, the same part often shows in different states. Existing and proposed arn't usually a problem because most of the times they come in different networks and you can select the whole network after Drefing and change the styles in one go. We often want to show demolition and provisional for some parts and while you can set it in the metadata for each pipe/structure, there's no way to reference the style by this value.

I think I'll go down the dynamo route but if someone has a solution already, I'd be happy to learn.

[Joe-Bouza]

Is the style in the part list only being used?

I have found if user changes the the style, instead of swapping parts, that style assignment won’t carry through 

[Joe-Bouza]

Is the style in the part list only being used?

I have found if user changes the the style, instead of swapping parts, that style assignment won’t carry through 

[chriscowgill7373]

Data referenced parts pull their style from their part id match within the parts list. So, if you override a style in your source file, it will not carry through.   If the style is different in the parts list in the child file, it will take on that style.  If you have existing and proposed, I would recommend an existing and proposed parts list, and keeping the networks separate.  These days, you can connect gravity pipes to structures in other networks, so that helps.

As for a dynamo way to look at it, there is a way to do it, where it can look at the pipe id and match the style from the parent file to the child file. @swalz are you able to possibly provide some guidance/pushes in the right direction on this?