Idea Details

Sysfilter to work in a sub resource.

Last activity 08-24-2018 08:23 AM
Ronald DSouza's profile image
05-18-2018 03:34 AM

Combine Resource is Created using

2 views 1.

  • Online: Partner_V
  • Online ParnterList_V

 

The table PartnerList_V is the used to create a resource with Partner_V join on PartnerID The issue is when we use SYSFILTER..Parnter = equal('PartnerName':'Something') we get a response with all records and only partner array with { "PartnerSiteID": 1, "PartnerSiteCode": "*********", "Name": "*******", "PhoneNumber": "*******", "Email": "*******", "StreetAddress": "****************8", "Suburb": null, "PostalCode": null, "ContactName": null, "ContactPhone": null, "ContactEmail": null, "StartDate": "2017-11-09", "Latitude":*******, "Longitude": ******, "IsServiceAvailable": true, "Category": null, "@metadata": { "checksum": "A:8e008f405b593a48" }, "Partner": [ ] } which is not correct, 

 

Can the filter be applied within the container combined resource


Comments

08-24-2018 08:23 AM

Raised a support ticket for this. They said it is by design

07-26-2018 01:14 PM

I got a similar issue:

When you define a custom resource, where you add a sub level that represents a Parent , is there any way to filter the result by data in the parent?  by example ; in a resource os orders you add a new level to customer to get customer Name, then if sent the Filter=customerName=‘xx” you get the error that that column doesn’t exit in datase, even if you put in the way customer.customerName=‘xx’ it fails. In the case you do in the way filter..subresource=columnName=‘data’ then you get null in the sub resource and what you want is don’t get that row where his parent doesn’t fits filter

05-18-2018 03:43 AM

After further research and testing, sysfilter will not work in a sub resource. Development team mentioned they indicated this how sysfilter currently functions. We would like t to work on "containers" so we are requesting this idea