Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..
106 views

\ in CI Names

Jump to solution

A decision was made to include backslashes in some CI names, and, as you can imagine, it's causing some problems.  The one I'm struggling with is viewing CI relationships for these CIs.  We've tried two methods, and both work in the desktop client but not in the web client.  In the web client, we still get the message "Cannot find related information in CM.relationship."

Method 1:

 

$fieldContents=cursor.field.contents()
if (($position=index("\\", $fieldContents))>0) then ($fieldContents=strrep($fieldContents, "\\", "\\\\"))
if null(cursor.field.contents()) then ($find.skip=true) else ($query="concatenated.name=\""+$fieldContents+"\"")

Method 2:

if null(cursor.field.contents()) then ($find.skip=true) else ($L.RelName=cursor.field.contents();$L.void=rtecall("escstr", $L.rc, $L.RelName);$query="concatenated.name=\""+$L.RelName+"\"")

 

Aside from reversing the decision to use backslashes in CI names, any other ideas how I can get these relationships to display in both the desktop and web clients?

 

0 Likes
1 Solution

Accepted Solutions
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: \ in CI Names

Jump to solution

Hello Goodja,

hope you are doing fine today.

I just wanted to let you know that this issue is a defect and was already fixed, please take a look on the link below:

https://softwaresupport.hpe.com/group/softwaresupport/search-result/-/facetsearch/document/LID/QCCR1E99739

Carlos Villalobos R
Customer Support Engineer
If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.

View solution in original post

0 Likes
1 Reply
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: \ in CI Names

Jump to solution

Hello Goodja,

hope you are doing fine today.

I just wanted to let you know that this issue is a defect and was already fixed, please take a look on the link below:

https://softwaresupport.hpe.com/group/softwaresupport/search-result/-/facetsearch/document/LID/QCCR1E99739

Carlos Villalobos R
Customer Support Engineer
If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.

View solution in original post

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.