Lennart

Can you create a view? I think you will need to create a new view and expose it to SData.

You can get to email address through SData but these are contained in the Collection associated with the Person object in the Schema.

Create a view like

Select * from person where pers_personid =

(SELECT EmailLink.ELink_RecordID FROM Email INNER JOIN

EmailLink ON Email.Emai_EmailId = EmailLink.ELink_EmailId

WHERE ((EmailLink.ELink_EntityID = 13)

And then you should be able to query for a person record referencing an email like

http://[servername]/sdata/[installname]j/sagecrm/-/vmyview?where=Email.Emai_EmailAddress eq 'mystring'

Additionally to this ....

API-Call:

cloud.na.sagecrm.com/.../Email

We get a reponse with all mail-adresses in the system.

The response looked like that (excerpt):

...

"Emai_EmailAddress": "[email protected]",

"emai_createddate": "2011-02-09T11:04:09-05:00",

"emai_updatedby": 1,

"Company": {

"$url": "">cloud.na.sagecrm.com/.../Company

},

"Person": {

"$url": "">cloud.na.sagecrm.com/.../Person

}

Both - the URL for company and the URL for person are not working.

The Tomcat is responding a 404 - The requested resource is not available.

Regards,

Robert.

In my opinion an api which provides these info's should also respond like that. This is a bug - isn't it?

Probably we could make this work with a view... the problem would be that every system has to by changed (adding the view) to make this feature work.

Regards,

Robert.

Hi together,

I just created a case on that.

A new view (even select * from company) will not be accessible via API.

This API-Call is working:

cloud.na.sagecrm.com/.../Company

This is API-Call is not working:

cloud.na.sagecrm.com/.../vcompanysdata

The message coming back from an Api-Test-Tool like “Postman” looks like this:

{

"$diagnoses": [

{

"$severity": "Error",

"$applicationCode": null,

"$message": "Die Ressourcenart ist nicht vorhanden. ",

"$stackTrace": "sdata851224",

"status": "BAD_REQUEST",

"$sdataCode": "ResourceKindNotFound"

}

]

}

Hi together,

I just created a case on that.

A new view (even select * from company) will not be accessible via API.

This API-Call is working:

cloud.na.sagecrm.com/.../Company

This is API-Call is not working:

cloud.na.sagecrm.com/.../vcompanysdata

The message coming back from “Postman” looks like this:

{

"$diagnoses": [

{

"$severity": "Error",

"$applicationCode": null,

"$message": "Die Ressourcenart ist nicht vorhanden. ",

"$stackTrace": "sdata851224",

"status": "BAD_REQUEST",

"$sdataCode": "ResourceKindNotFound"

}

]

}

Views should be available

See: community.sagecrm.com/.../using-sdata-to-exposing-group-like-data-to-an-external-application.aspx

Possible reasons that you are getting an error is

1) The meta data needs to be refreshed. - You may need to restart IIS.

2) The request is case sensitive and the resources in SData will be lowercase - make sure you have the name of the view correctly referenced.

In the case of cloud, then this should be refreshed automatically when the instance is next restarted.

Hi Jeff,

I've done a MetaData refresh already. Yes it's Cloud - so a restart is not possible for me.

Concerning the Name I tried already lowercase/capital/case-sensitive.

Can you tell me how often the "instance" is restarted? Is there a possibility to force a restart at our instance?

Thanks in advance,

Robert.

Robert

I think you will need to wait for the support team to respond to the case that you raised.

Hi Jeff,

just got an answer from the support...

The older API (sagecrm vs. sagecrm2) is working...

https://cloud.na.sagecrm.com/sdata/affinisapplicationservicesGmbHCo874jpsylcj/sagecrm/-/vcompanysdata#

Regards,

Robert.