Hemal Jadav said:

I have got to fetch invoice list with some data which doesn't show follwoing data by $detail or by $children

$detail is not a keyword in Sdata so will have no effect. $children is a keyword but specifying this won't work because the address relationship to an invoice is defined as association i.e. is not a child. You can see this if you issue a $schema request where you will seethe relationshiip defined as such:

<xs:element name="postalAddresses" type="sc:postalAddress--list" sme:relationship="association" sme:canGet="true" sme:isCollection="true" minOccurs="0"/>

Hemal Jadav said:

2. custom fields like Analysis 1 uunser invoice

These are not exposed to Sdata at all I'm afraid.

Using Sdata the closest you could get to what you are trying to do is to include postalAddresses e.g.

http://localhost5495/sdata/accounts50/GCRM/-/salesInvoices?count=1&include=postalAddresses

With that you will get the invoice with all addresses related to it, including the delivery address, but as I say you can't get the analysis fields at all.

Hemal Jadav said:

Is there anyway i can define layout in sage with required data and can access the same using sdata url?

Afraid not. That isn't how Sdata is designed or works. If you are designing a layout and want to access the data it produces you would need to use the Report Designer API - details are available in the SDK documentation. Note - unlike Sdata ,which is an open standard and freely documented, you need to be a member of the Developer Program to use and access the SDK and it's documentation.

Hope that helps

Hi Darron

Thanks very much for the update and guidance.

we are using web based application to fetch the data and we are left with no choice other than SDATA as we won't be having access to sage 50C accounts machine.

Would being able to use and access the SDK help us achieve  what we are looking for?

Appreciate your repsone in advance

Kind regards

Hemal

Hemal Jadav said:

we are using web based application to fetch the data and we are left with no choice other than SDATA as we won't be having access to sage 50C accounts machine.

You must have access to the machine though as otherwise how could you be querying the Sdata endpoints currently? The only things from a technical perspective that would be different between using Sdata Vs SDO (Sage Data Objects - the eternal developer SDK) to access the Accounts data is the specific technology used, and the ports you would need open to allow your application through.

There may be other considerations such as security concerns about allowing a web server direct access to your Accounts data, particularly if it is a publicly facing server, but they would be the same regardless of the specific technology you use to access the data.

Hemal Jadav said:

Would being able to use and access the SDK help us achieve  what we are looking for?

Based on the info in your original post I would say yes. You can most certainly access invoices and their delivery addresses, as well as all of the analysis fields using SDO.And as I alluded to above you can also do things like defining your own layouts and run/export data using these via the Report Designer API (part of the same package as SDO).

If do want to consider using SDO if you email [email protected] they will be able to advise on how to go about joining the developers program and associated costs, etc.