CS extra fields in Rest API

Hi.

We have a lot of CS extra fields on our objects.

Contact has an x_objectguid and x_code.

I am not able to see or change/create this using REST API.

How do I do this?

Espen

RE: CS extra fields in Rest API

Hi Espen, 

The Rest APIs does not support the Service module as of this date - it is under implementation, and if you want to fetch the extra fields, you'll need to create a CRMScript that fetches it for you, or fetch it directly from the database.

 

By: Simen Mostuen Iversen 5 Feb 2019

RE: CS extra fields in Rest API

This is really really bad!

When we chose to upgrade from CS 7 to 8 it was because Sverre Hjelm in a meeting told us that CS was now fully supported in REST. We had a lot of other CS-systems that we considered, but because of this we chose to do this.

We have really been struggling to make this work and now we feel we have been fooled!

We need to create and read contacts, persons and tickets from code with x_parameters.

I have been using SODB class to do some of this, but I am not able to make this work after the upgrade so I was going to move this to REST. 

What is the timeline for this now??

Espen

By: Espen Fosshaug 5 Feb 2019

RE: CS extra fields in Rest API

If Sverre has said it is supported, then it must be.

I knew it was in planning, but not that it was already available.

 

Then I apologize for giving my 2 cents, because then I honestly have no idea.

By: Simen Mostuen Iversen 5 Feb 2019

RE: CS extra fields in Rest API

Hi Espen,

Don't worry, the REST API's are under continous development, and I believe you have already been testing some of them. Information just flows slowly sometimes :-) The current status is that our latest release supports Tickets/Message CRUD operations with standard extra fields (x_*), as well as extra table (y_*) CRUD operations.

We currently do not support REST operations for CS extra fields on company/contact, but it is on the backlog and I hope we will get that fixed quite soon. Stay posted for updates.

Sverre

By: Sverre Hjelm 5 Feb 2019

RE: CS extra fields in Rest API

Thanks Sverre - we are currently not able to create companies the way we used to.

But then I have to figure out what is wrong there. Looks like some login-problem on the SODB class.

Espen

By: Espen Fosshaug 5 Feb 2019

RE: CS extra fields in Rest API

SODB is unfortunately outside my knowledge area. Perhaps someone else can help out. Do you have any more specifics about your problem? Perhaps some failing code?

Sverre

By: Sverre Hjelm 5 Feb 2019

RE: CS extra fields in Rest API

I have SO gurus in the building. We will figure it out :-)

Espen

By: Espen Fosshaug 5 Feb 2019

RE: CS extra fields in Rest API

Hi Espen,

When you say SODB, are you referring to the COM API? This is not the forum for COM questions...use the Windows Client forums.

With regards to  REST, are you not able to select x fields using the dynamic archive provider?

/api/v1/Archive/dynamic?$select=contact.name,contact.x_objectguid,contact.x_code

Frode Lillerud has created a nice blog post that describes how to use CRMScript to build custom REST endpoints in Service that may fix your existing limitations. 

Hope this helps!

By: Tony Yates 5 Feb 2019

RE: CS extra fields in Rest API

Hello Sverre,

The current status is that our latest release supports Tickets/Message CRUD operations with standard extra fields (x_*), as well as extra table (y_*) CRUD operations.

This is awesome news! Just pulled the latest NetServer Services release from NuGet and found the "Extra" StringDictionary on the TicketEntity, TicketMessageEntity!

But where is the functionality you mention to do CRUD on a CS extra table? Can't find it in the 8.4 R5 release. (both REST and NetServer Services).

By: David Hollegien 5 Feb 2019

RE: CS extra fields in Rest API

The Extra field will shortly be renamed to ExtraFields to match the other entities in the service API. Continuously evolving.

By: Christian Mogensen 5 Feb 2019