Tuesday 15 September 2015

acumatica - Filtering on Customer Screen does not use more than one filter -



acumatica - Filtering on Customer Screen does not use more than one filter -

i using ar303000 screen search customer. if add together more 1 filter first filter applied. also, results set not include generalinfomainaddress lines. may why filter not working.

ar303000content ar303000 = context.ar303000getschema(); context.ar303000clear();

list<command> cmds = new list<command>(); cmds.add(ar303000.customersummary.servicecommands.everycustomerid); cmds.add(ar303000.customersummary.customerid); cmds.add(ar303000.customersummary.customername); cmds.add(ar303000.generalinfomainaddress.addressline1); cmds.add(ar303000.generalinfomainaddress.city); cmds.add(ar303000.generalinfomainaddress.state); cmds.add(ar303000.generalinfomainaddress.postalcode); list<filter> filters = new list<filter>(); filters.add(new filter() { field = new field() { fieldname = ar303000.customersummary.customername.fieldname, objectname = ar303000.customersummary.customername.objectname }, status = filtercondition.contain, value = "doe, john", operator = filteroperator.and }); filters.add(new filter() { field = new field() { fieldname = ar303000.generalinfomainaddress.addressline1.fieldname, objectname = ar303000.generalinfomainaddress.addressline1.objectname }, status = filtercondition.contain, value = "255", operator = filteroperator.and }); var ar303000export = context.ar303000export(cmds.toarray(), filters.toarray(), 0, false, false); homecoming ar303000export[0][0];

the web services can filter on fields of primary view of screen, in case ar303000.customersummary. if seek filter on else, scheme doesn't throw exception, instead silently discards filter.

if need able filter information, suggest create generic enquiry joins on tables need, , utilize gi screen through web services other enquiry screen.

acumatica

No comments:

Post a Comment