Sdata pulling through names rather than IDs, despite the Sdata Schema showing that the type is xs:integer

Posted By simonc over 7 years ago

I have observed that Sdata calls to various tables are returning the names rather than the ID of fields despite the type for the field showing as xs:integer in the schema (and hence indicating that they should be IDs).

Instances where I have observed this:

Table: communication

Fields: comm_createdby, comm_updatedby

Table: person

Fields: pers_companyid, pers_created_by, pers_updatedby

Is this a bug? Or a setting? If the latter where can I change it to actually get the IDs?

Thanks

Parents

0 Sage CRM over 7 years ago

Simon

I don't know if this is a bug or a feature. I suspect that this is a result of the way in which the data passes through the application layer. If you think about lists that are displayed in the system then the fields that are 'look ups' to the user do not show the actual value of the foreign or primary key. You may have to use a technique like this

See: community.sagecrm.com/.../but-i-really-really-need-to-see-the-actual-oppo-opportunityid-displayed.aspx
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Sage CRM over 7 years ago

Simon

I don't know if this is a bug or a feature. I suspect that this is a result of the way in which the data passes through the application layer. If you think about lists that are displayed in the system then the fields that are 'look ups' to the user do not show the actual value of the foreign or primary key. You may have to use a technique like this

See: community.sagecrm.com/.../but-i-really-really-need-to-see-the-actual-oppo-opportunityid-displayed.aspx
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data

Sage CRM

Sdata pulling through names rather than IDs, despite the Sdata Schema showing that the type is xs:integer

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING