Understanding the function of "Create a new representation" and "Republish"

If you are using latest for the representation definition, yes, it can be changing frequently. We used as-stored which uses a the check in baseline so its fixed from lower updates. To answer your question about creating new vs republish, your call, both achieve the same result. You can have any number of representations listed which can be done by using "Create new" and giving it a different name. It does not impact previous publishing. Republishing regenerates an existing representation such as the default if you only have one. Depends if you want to keep old ones when generating an update. There are also carry forward options that can be configured as well as position assemblies which pull lower representations of components instead of making copies.   I believe there are also schedulers that can be run to regenerate out of date representations (where lower components have been updated). Hope this helps.

@SR_10832839 ,

Republish will use the original configuration and will modify the existing dB entry for the rep and the links from rep to the files in the vault created by publishing.

The dB data beyond the rep and the links will be deleted from the dB and new data will be created and linked to the existing links that connect the rep to the files in the vault.

The original files in the vault will remain but they will be "unreferenced".

Create New Rep creates a second rep independent of the first rep.

So, if you are publishing the existing rep with config Latest republish would get the job done.

Makes sense?

David

Hello @SR_10832839, 

It looks like you have some responses from our community champions. If any of these replies helped you solve your question, please mark the appropriate reply as the Accepted Solution. 
Of course, if you have more to share on your issue, please let the Community know so other community members can continue to help you.

Thanks,
Vivek N.
Community Moderation Team.