topic Re: VBOs with same name in Product Forum

VBOs with same name

Neel1 — Thu, 12 Dec 2024 14:59:48 GMT

using BP version 7.0 - I have two VBO as visible below. The one under Web API is older one and other one is new.

When i am selecting the bottom one in action and click on okay. VBO got changed to Web API one.

What can be possible reason for this. i now renamed the bottom one to avoid the conflict.

Re: VBOs with same name

Tejaskumar_Darji — Fri, 13 Dec 2024 11:33:34 GMT

I tried to reproduce the same in the latest 7.4 and observed the same, this is indeed a bug.

If we have the same name of Object and WebAPI then it does not save the Action information.

Re: VBOs with same name

AmolJangam — Fri, 13 Dec 2024 13:37:11 GMT

It is not bug but intended behavior of Blue Prism.

Since a Object ID is created in database, your new object will get redirected to the same even though you create different version with same name.

While Importing object with same name BP will ask for overwriting and if you choose not to then such issues occurs, where earlier version is given preference.

Re: VBOs with same name

Tejaskumar_Darji — Fri, 13 Dec 2024 13:42:24 GMT

HI @AmolJangam This issue involves one object and one Web API sharing the same name, not two objects with identical names. You can try it out to get a clearer understanding of the problem. It looks like the conflict is happening due to name and not the ID.

Re: VBOs with same name

ewilson — Mon, 21 Jul 2025 13:52:13 GMT

@Neel1

The SharePoint connector was converted from a Web API Service to a VBO back in May 2024. It was given a new Object ID, but the name was kept the same. As far as the DB is concerned, they are two different items. In hindsight, we probably should have changed the name slightly.

The best solution to address this now is to simply archive the old Web API Service definition. It should not be used any more.

Cheers,
Eric

Re: VBOs with same name

Neel1 — Mon, 21 Jul 2025 13:58:43 GMT

Thanks @ewilson for replying here and Yes, a different name could have avoided the confusion. but we are sorted here. Once i imported the VBO version , i removed the web API version.

Re: VBOs with same name

Kirk.Russell — Wed, 23 Jul 2025 13:58:16 GMT

Hi @Neel1 I'm curious, did you already have actions built using the old web version?

I can't see a way of doing this without breaking all my current SharePoint actions, if I change the name of the web version the actions break, if I retire the web version the actions break. If I rename the incoming vbo version to use it while the web version is intact to help with configuring the actions, on next release of the vbo version they will still be different vbos and the actions need reconfiguring again to use the standard name version?

Hi @ewilson simply archive the old web api version doesn't really cover the impact on current actions? Or am I missing something here?

Regards

Kirk

Re: VBOs with same name

Neel1 — Wed, 23 Jul 2025 14:37:16 GMT

hello @Kirk.Russell - We have both the Asset [ Web API + VBO ].

There are few automations which are using Web API version and latest Processes which we are building are using the VBO one and there is no issue coming in using both differently.

My earlier response was with respect to my Sandbox env where i removed/delete Web API one . i should have make it more clearer.

Below is how we have name the asset for clearer segregation

VBO one is with this name.

Web API one is with below name.

Re: VBOs with same name

ewilson — Wed, 23 Jul 2025 18:41:34 GMT

@Kirk.Russell if you have automations that are using the older Web API based SharePoint connector, you should plan to migrate them to the newer VBO. Archiving the Web API connector while it's still being used would cause those processes to break.

Cheers,
Eric

Re: VBOs with same name

Kirk.Russell — Thu, 24 Jul 2025 12:08:39 GMT

Thanks @Neel1 @ewilson

So my options for migrating are either:

Leave the web api in place, rename the newer vbo and then build and swap all the actions side by side, delete the web api but then need to do a similar migration with the next vbo update as the import wouldn't update the renamed vbo

Remove the web api and then have to rebuild all the actions from fresh with the newer vbo

Definitely not the smooth migration I'm used to with BP objects.

Kirk