Announcement

Collapse
No announcement yet.

How to prohibit to use special symbols in Object Id

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • How to prohibit to use special symbols in Object Id

    Dear ALL,

    Is it possible to prohibit to use special symbols (e.g. ,.'; when creating Object Id?
    Business number generator is not suit for us.

  • #2
    Re: How to prohibit to use special symbols in Object Id

    Use Action Check on the AUDIT action of object created, For Example - SHIPMENT - CREATED.
    -------
    Thanks and Regards
    Anurag Saini
    MavenWire

    Comment


    • #3
      Re: How to prohibit to use special symbols in Object Id

      Many OTM users have made this request to Oracle. Oracle has already created an enhancement/bug and its not yet targeted for a future release. Till then you have to train users not to create ID's with special characters.

      Certain characters such as less than, greater than, single quote, double quote, parenthesis, pound sign, caret and period will not work in Xids (OTM ID fields). In general you should only use letters A-Z, numbers 0-9, space, dash, and underscore in Xids if you want to be assured of everything working correctly.

      An Enhancement has been logged to perform the XID validation to not permit this character use in the UI. This bug is targeted for future release and not yet implemented at the time of this note authoring. For information on this Enhancement, please review the following enhancement bug:

      Bug 9857578 - SUPPORT SPECIAL CHARACTERS

      Comment


      • #4
        Re: How to prohibit to use special symbols in Object Id

        Create Action check and assign it to the users/roles. This would stop from saving the Object which doesnt satisfy the condition mentioned in Action Check

        Comment


        • #5
          What will be the issue, if I create any location or contact id with comma. Example : DC01, Utrecht Warehouse.

          Comment


          • #6
            The issue with comma may not be apparent initially, but you won't be able to search for this location with the One Of selector, and of course when you export/import to/from Excel using CSV, this could cause issues if the field is not delimited with double quotes. I've even seen issues with XID's start with a number, for example 40_FOOT_CONTAINER...

            Comment

            Working...
            X