(Rome) Source Control for Scoped Plugins error: "An App Customization already exists for this application, install it to make customizations to your application"

[Christopher Cro]

This question is regarding the new Rome feature (which is now available for PDIs) that enables Source Control for customizations to Scoped Plugins (such as CSM/HR).

I tried to test out this new feature with the CSM plugin today using a fresh Rome PDI (Release Candidate 2), but I am encountering a showstopping error message that prevents linking to source control: "An App Customization already exists for this application, install it to make customizations to your application".

Let's walk through what I've tried so far, so you folks can put forth suggestions or try to reproduce the issue:

1. Created a new Rome PDI (Release Candidate 2)
2. Created an empty git repo for the application customizations
3. Configured known working https git credentials as a Basic Credential record
4. Installed the Customer Service plugin
5. Opened Studio
6. Selected the "Customer Service" application
   NOTE: I've also attempted this same process via the "Select Store App to Customize" button. When I did that, I was prompted to follow the exact same steps seen below and arrived at the exact same error
   
7. Encountered this message, indicating that I should be able to use Source Control features
   
8. Opened the "Link to Source Control" menu
   
9. Filled out and submitted the "Link to Source Control" dialog
   
10. The operation fails with the aforementioned error: "An App Customization already exists for this application, install it to make customizations to your application."
    
11. Despite failing, I can see that some dummy commits were made to the specified repo, though no new branches were created. Studio still shows that Customer Service is unlinked.
    NOTE: It didn't make any difference when I tried again with the repo in this state vs. when I deleted the repo and tried again from scratch.
    
    

[monkalope]

@Daniel.Draes Do you know if this is also restricted for Demo instances? TIA

[Daniel Draes]

As we need the link to the AppRepo with a defined customer prefix I would assume yes, demo instances will have similar problems unless they a customer owned instances.

[Bradley Marin]

Hi Daniel, sorry to rekindle an old thread. I'm wondering if this has at all changed over the years? I'm getting the same error as above and am quite disappointed I can't mess around with source control in my PDI.

[Rohant Joshi]

@Daniel Draes  thanks for checking with the product, but I am surprised because I am seeing a similar error on my customer instance, we are trying to push to "GRC: Business Continuity Management core" to GitHub but seeing a similar error.
Do you mean the first step for us is to sync it with the repo and only then we can push the app to Source control?

[Daniel Draes]

When you say similar error... is it the same or not? Pushing to GIT should not pose a problem I would think. Publishing to the repo.. yes.