Exporting Project Parameters to a shared parameter list?

[m-de-lange]

The title says it already, is this possible in some way?

[Mirko.Jurcevic]

I don't understand the question.

What project parameters? Those which are added to project to different categories?

Or you are talking about Shared parameters that are added to the project?

Or something else?

Whatever it is, if it's not already shared parameter, then it can't be done. You can't just like that "convert" any parameter to a "Shared" parameter.

[m-de-lange]

I'm talking about Project parameters.

Parameters that have added to only the project. Thus aren't shared.

Is it possible to export these project parameters to a shared parameter list? This to keep the guids the same.

If we recreate the parameter it'll have a different guid number and can cause issues with the existing project parameters.

I don't expect this to be possible, I was merely curious.

Hope it's clearer like this!

[Mirko.Jurcevic]

Don't mind me ask, but why do you want to do this?

If you want to keep the GUID between the projects, that's what shared parameters are for.

Maybe it's possible only to export project parameters with their guids with the help of Revit API, but not in the shared parameters file, it will mess it up.

As far as I know, Revit API can't create project parameters, don't know about getting information about them.

[m-de-lange]

It was a curiosity if it's possible or not.

It's also a little unethical I suppose since you can just create it as shared parameter and replace the project parameter with the shared. The Guid won't be a problem then.

Man i'm a genius!

Thanks for the guidelines

[Mirko.Jurcevic]

What do you mean "replace it"? You can't replace it.

You will end up having two parameters with the same name (one project parameter and one shared) which will leave you to figure it our which is which.

No problem. 🙂

[m-de-lange]

Well no, not exactly replacing it. 

More like creating the same parameter as shared, inserting it in the project and applying the right categories. After that remove the old, and voila.

[Mirko.Jurcevic]

I understand.

Using shared parameters, however, has more advantages, but it depends on the need.

[hmunsell]

I had wondered the same thing at one time. I made all these project parameters and then descovered Shared Parameters and wanted to convert them all to a Shard Parameter file. To my knowledge, No, there is not way to export out the project parameters to a Shared Parameter TXT file. likewise there is no way i know of to change a Projector Parameter, that is already created, to a Shared Parameter. 

[Mykola.kolomoets]

Mirco, let me explain the problem.

We have some Revit template for some task automation. This template uses diffierent parameters, partly project parameters (due to historical background and our skills developing during a time) and partly shared parameters. Also there are different templates made by different authors.

Now I want to combine knowledge and databases in order to create common parameters naming, common template principlec and so on.

So, I need to collect all parameters from different projects, rename these parameters and save them in external parameters file.

That's why it;s needed to export project parameter into a shared one, but the most difficult task - to keep template usable after this. It works if done manually, using option "Export..." in a project parameter setting form - after you export this parameter, you can rename it directly in parameter file, import to new template and all features using this parameter will work perfectly. This means that somehow Revit database makes a correspondence between parameter definition and its shared representation when creates GUID. 

But I don't see how can it be done using ExternalDefinition and InternalDefinition classes, cause they have no key available for both. If I will use simple DefinitionGroup.Definitions.Create(newParamOptions) function, it will simply create new different shared parameter with the same name, but the template will not work.

There certainly exist a solution if it works doing manually, but could you help me to find the way, please?

[andryS3MN2]

For anyone still looking for an answer to this. It is pretty simple.

1. Go to the manage tab.
2. Click on Shared Parameters
3. Create a new shared parameter file in the desired location.
4. Click OK
5. Go to the manage tab.
6. Then click on project parameters. A list of parameters should appear.
7. Double click on any parameter in the list to bring up the "Parameter Properties."
8. Click export. (This should add the shared parameter to the most recently created text file)
9. Click OK on the prompt
10. Go back to Shared Parameters and you should see the project parameter listed in the shared parameter file.

FYI, not all project parameters can be converted (the export option will be greyed out) I don't know why, yet.

Also here is the link to the Autodesk tutorial: Export Shared Parameters to a Shared Parameter File | Revit | Autodesk Knowledge Network 

[iainsavage]

Get DiRoots One addin (from their website or Autodesk app store) and use the Paramanager tool to export and import several/all parameters with a few clicks rather than doing it one at a time.

Project parameters can be exported to a shared parameters file, then imported into other projects/families.

[hmunsell]

@andryS3MN2 The problem with what your showing is that only works if the Project Parameter was made from a Shared Parameter to start with.

If the parameter is just a Project Parameter, the Export option is not selectable. 

[sk_jungWLUEA]

do you know why only some of them are able to export from that menu you talking

[iainsavage]

I think @hmunsell explained that at part 13.

See my response at part 12 - I tested it before posting and it works:

"Get DiRoots One addin (from their website or Autodesk app store) and use the Paramanager tool to export and import several/all parameters with a few clicks rather than doing it one at a time.

Project parameters can be exported to a shared parameters file, then imported into other projects/families."