Publish fields of CardPart in Web Service

einsTeIn.NET

Hi guys,

I'm trying to create a Web Service based on a page that only consists of "subpages". It contains a ListPart and a CardPart and it's fine in RTC. But in the Web Service I only see the fields of the ListPart. It doesn't matter if the CardPart in the FactBoxArea or not.

Any idea?

kine

THe webservices are able to publish only basic pages, like header with lines. I am afraid that what you have described is not "in the limits".

einsTeIn.NET

](*,) Is that true?! Is there some kind of official statement from MS? If I take a look at the online help or some of the msdn walkthroughs I don't find any limitation. They only talk about "pages". So, from my point of view this should imply all types of pages.

Are there any additional limitations that aren't mentioned in the official documents?

kine

Like problems with temporary tables? Filtering to flowfields? ...


there are many issues, thus it is better to stick to basic simple page design. e.g. how you want to publish list with CardPart - take it from the DataSet point of view:

You have 10 records in the list - ok, no problem
You have 1 record in the CardPart for the active records from the list - ??? In web service, which line is "Active"? Which records should be there? There is no way to read All records you need, the CardPart shows only one record, you cannot expect to publish whole dataset...

einsTeIn.NET

kine wrote:

Like problems with temporary tables? Filtering to flowfields? ...

Yeah, those ones. Although temp tables issue is mentioned somewhere, already read that.

kine wrote:

there are many issues, thus it is better to stick to basic simple page design. e.g. how you want to publish list with CardPart - take it from the DataSet point of view:

You have 10 records in the list - ok, no problem
You have 1 record in the CardPart for the active records from the list - ??? In web service, which line is "Active"? Which records should be there? There is no way to read All records you need, the CardPart shows only one record, you cannot expect to publish whole dataset...

That's right. But in my case the FactBoxes belong to the header, not the lines.

kine

Still, I think the biggest issue is to use Card to publish. Lists are not problems, but cards... you filter to have 10 records, but card is displaying one. It means it send one? Or all 10? Which is the active ona?

Can you see the logical problem in this? 8)

einsTeIn.NET

Ah, I think I know what you mean. In my case there should be only one header available.... :-k
It should... but what if one header hasn't been consumed (e.g. because of technical reasons) and the next one is going to be published :?:

What if I transform my FactBoxes also into ListParts that show only one record?

Or do you suggest a completely different solution?

kine

we are using just list pages if possible, without subforms (or subform only in header-lines situation). In more complex cases we are using functions with xmlports to be abel to work with complex structure (but it doesn't support paging).

einsTeIn.NET

I put everything in different ListParts now. So, there are lists that only contain one record and lists that contain several records. All lists refer to one header then. And if there are more than one header then I get another node in the xml. That's fine for me.