Not sure about the exact context around the objects or reasoning, but if there is any relationship at all, the period character was the cause of many headaches while fixing CBS issues back in the day (probably about 12 years ago). The period character was in primary keys (I think it was in the part number), and CBS was playing up with strange errors that were difficult to decipher. You might be able to dig up some more info in the knowledge search. There is a system parameter - “Define the characters which should not appear in Key Fields”, which has the period key added in as default to possibly avoid these issues.

Hi Asanka,

Thank you very much for the reply. I tried using the mentioned setting. I could not find it in Aurena, so I defined it in IEE instead and re-executed the same test flow. But still I get the error. Is it correct to set the parameter “Define the characters which should not appear in Key Fields”  in IEE, or is there anywhere else to set this specifically for Aurena ?

Best Regards,

Thilini

Hi,

> Question 1: Is there any specific reason as to why period sign needs
> to be avoided?

Yes. If one of the key values contains a period, and if you use a period as the separator when inputting the value, then the system cannot know when the period is used as a separator and when it is used in a value.

Regardless, we have thought about this and the solution is simple: read what the message says and follow the instruction :)

The message says:

  "If one of the values contains a period, you can use a comma,
   semicolon, or colon as a delimiter instead."

This is the scenario we have here. So the solution is to use, for example, a comma instead of a period.

For example, if the Site is 1 and the object ID is S1.MD, you enter this:

1,S1.MD

Then save. It will work. I just tried it.

> Question 2: Then as a workaround, if you connect the object using
> objects tab in the document revision form, object description is
> not displayed until you save the record. (However the object can be
> connected without getting the delimiter error).Is this something
> that should be corrected, so that user can see the description,
> before saving the record ?

I don't understand this, sorry. When I try to use the Objects tab it inserts the object description when I have selected an object from the LOV:

Thanks!

/Mathias
 

Hi Mathias,

Thanks for the reply :)

I agree that the information message gives a workaround. But I’m not sure whether it is useable for the customer, since from equipment side, we have already allowed period sign in object ID and customer has created objects with period sign. After creating the functional or serial objects, they cannot change the ID to use comma, instead of period icon. Please correct me if I’m wrong. However, my object ID is ID.DOC.TEST1 and tried to connect with key 1,ID.DOC.TEST1. Same error was raised.

The workaround is in Aurena :)

Before saving:

Best Regards,

Thilini

Sorry, I missed that this was for Aurena. The functionality should be the same though.

The customers don’t need to change their IDs, they need to change the way they input the IDs, in Docman.

I just tried in Aurena on Apps 10 too and I could connect the object with the ID S1.MD (on site 1) to my document by inputting the following value:

1,S1.MD

PS. You should not input anything in the Key Ref field unless you want to use that instead of entering the much easier key values.

PPS. Tested with your value now and it failed for me too. I think we might be doing some guessing behind the scenes of what the separator is (it could either be a period or a comma in the case of “1,ID.DOK.TEST”), and in this case it fails. It’s in these cases where the user can/should provide the LOV to select the object.

PPPS. This works in IEE, I hope we should be able to make it work in Aurena too though. I think you should create a task for it. And please link to this discussion.

Thanks Mathias, I will send an RnD task for the Aurena issue. And thankyou very much for other responses aswell.

And I will include the first issue as well, because the workaround will work if the object ID has only 1 period sign included. If there are 2 more period signs, same error is raised.

Eg:

Object ID S1.MD in site 1 - Enter as 1,S1.MD - This works.

Object ID S1.MD.MD in site 1 - Enter as 1,S1.MD.MD - Same error raised

Thanks! Does the customer have more than one period in their object IDs?

Yes Mathias, the example object ID from customer is 10.L0481.0.D.P

This is fixed in App 10 Update 13 (Solution ID 293900)