Dear all,
just started with a lot updates of Forge Components.Often I get the message "Module or extension name already exists" and I'm not able to continue.Obviously the message is correct, but it's concerning a existing module of the application to be updated.Sometimes I just delete the old one, and install the new version, but this is not always possible, for example if the component also has a DB entity, which is already filled.Any idea how to fix this? And why suddenly these messages appear (while updating components)?
Also a second question/discussion.When I use a Forge Component which is consuming OutSystems UI, and OutSystems UI is updated, then this Forge Component automaticly will be a custom version (also indicated when trying to update this component).Should the owners of this component always create a new version, consuming the new OutSystems UI?Best regards,
Jeroen Vormer
Hi @Jeroen Vormer
It’s generally best to follow a clear naming convention for application modules in your environment. For example, add a prefix at the beginning of the module name, such as AL_, MYAPP_, or any company/project-specific initials like XX_.
This way, each module will always have a unique name, and you’ll avoid conflicts when installing or updating components from Forge. When you download a new Forge component, you can also rename the modules accordingly before integrating them.
Hope this helps!
regards,
Manish Jawla
@Manish Jawla ,Probably you misunderstood my question!I'm updating a Forge Component, which contains obviously the same module-name as I already have!Then I receive this message/error.Best regards,Jeroen Vormer
Which component you are trying to update it.
@Amit J
I had several. From my mind for example 'Ultimate PDF' and 'BDDFramework'.
Can you check the log details. from service center the same env.
@Amit J No log present regarding this message.I'm using the "Forge Updates" feature from Service Studio, and the messages appears in the Forge itself.
One more thing, take a look at this. You might be upgrading from a traditional system to a reactive one.https://www.outsystems.com/forums/discussion/73164/ultimate-pdf-how-to-upgrade-ultimatepdf-to-version-4-0-0-or-higher/
I tried with ultimate pdf and getting same error
@Amit J Indeed if you select "Install anyway" you'll receive this error.