Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
@casquatch One of the problems with transfer project standards is you can transfer none or all and I think get a choice about overwriting ones with the same name. There isn't a method to transfer one out of 50 filters. I don't have an opinion about import/export vs transfer project standards, but more granular control is needed. An efficient way to copy settings of applied filters between templates and projects would also be useful.
@jkidder, I would agree, but the original idea was for a way, and there is. Autodesk seems to want these ideas very specific.
It would be nice to have a simple quick way of bringing them across, preferably like the Insert View from file tool where you choose to "Transfer project standards from a file", with granular options for selecting what you are bringing across (down to individual items, like the Purge tool).
As for the current setup...
Often times I will open a new blank file, transfer to that and remove any items that I don't want to transfer to a new file. After I have that cleaned up, I then transfer again from the new file into the project I wanted to just grab a few things from.
No, not ideal or quick, but it does at least give me what I want and not extra trash from the older project I'm transferring from.
BUT, I do totally agree there needs to be a simple way to make this happen.
Thank you everyone. I think that having the ability to export out a specific filter, versus all that's in the model would be efficient. To bring in all, but only need one, that creates more trouble than it's worth. This is similar to Navisworks views, where, before you can export any views, you pretty have to manually delete all other views prior to exporting. Otherwise, you end up having other views that you don't need also. Good discussion, though. Cheers!
