Hello everyone, I experienced an error when attempting to create an Integration Object that happened to have the same name as a cloned application.

I had created a cloned application of the Service Request, SR, application named XXSR. At a later date, I had a requirement to create an Integration Object to the OOB Service Request object and I attempted to name it XXSR but I received an error message similar to the message for a duplicate Integration Object, attached image of the message.

There are OOB applications that have similar named Objects.

Anyone know what is being checked here where an Integration Object can not have the same name as an application?

------------------------------
Neil Wornes
------------------------------

#AssetandFacilitiesManagement
#Maximo

As far as I know there isn't any published documentation on this (I could be wrong), but I did some snooping since I was able to reproduce this in my environment.  The FldOSName class does an explicit check to ensure that the object structure is not named the same as an application.  I have some guesses as to why, but they are just guesses.  It's likely to avoid naming conflicts with regards to REST/OSLC/WebServices.  In any case, it's an interesting quirk, but I wouldn't attempt to bypass it unless absolutely necessary.  I hope this helps.

------------------------------
Daniel Brame
Senior Technical Consultant
Intelligent Technology Solutions
dbrame@webuildits.com
www.webuildits.com
@dbrame/@webuildits
------------------------------