function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Juan RomeroJuan Romero 

Custom field names in XMLRPC describe call

Hi there,

I am working on a process to move accounts back to leads. As I was matching the columns I realized the names of the custom fields are 15 characters long (case sensitive). Even if I request case insensitive ID's, the server still returns 15 character ones.

Is there a way to get the 18 character IDs? Will I ever run intro trouble with duplicate case insensitive field names?

Thanks!

DevAngelDevAngel

Hi Juan,

I've logged a bug for this issue.  As a workaround you can use the algorithm for converting to caseSafeIDs if you need to.

(rename the attachment from .tx to .txt.)

Message Edited by DevAngel on 10-01-2003 09:09 AM

Juan RomeroJuan Romero

Thank you DevAngel, I appreciate your help.

You had given me the algorithm before. I already have a component I made that produces the ID's  >: )

DevAngelDevAngel

Hi Juan,

Remember that when you are converting the id to manage the cf_  properly.

Juan RomeroJuan Romero

I remember reading about the cf_ . I believe it was used for custom fields but I cannot remember what it was for. Care to remind me?

Thanks in advance.

 

DevAngelDevAngel

Hi Juan,

That's right.  All custom fields start with cf_ because starting an element name with a numeric is not allowed in the xml or soap specifications.