Microsoft Dynamics AX (Archived)

Filter field selection dropdown in SysQueryForm

(0) Share

Report

Posted on by psined

Hi, I have created a very simple query off of CustTable and specific fields:

7357.l1.png

When I run this query and choose from range fields drop-down I see everything:

5710.l2.png

How can I make the drop-down lookup only pull the 2 fields in my datasource? Is there a way to apply a filter to the Field lookup at all without major programming effort?

*This post is locked for comments

I have the same question (0)

All responses (10)

Answers (0)

Mea_ 60,284 on at

Like (0)

Report

Hi psined,

You cannot do this without changing code and it won't be easy one.

Was this reply helpful? Yes No
psined on at

Like (0)

Report

Thanks, I suspected that. I had to ask though because one of the solutions which we are working on starts off with generic query and leaves it up for the end-user to refine the ranges. However we want them to be able to choose designated fields only. Would be nice to have this added to SysQueryForm as an option/parameter as I can see many applications where this would make a world of sense..

Was this reply helpful? Yes No
Mea_ 60,284 on at

Like (0)

Report

You can go ahead and implement it but please be aware that this functionality is used across whole application and it could a breaking change.

Was this reply helpful? Yes No
psined on at

Like (0)

Report

Would you have a recommendation as to how best to implement? Create a custom form and associated controller class (as a copy of SysQueryForm), or customize the existing one? What would you do? :)

Was this reply helpful? Yes No
Martin Dráb 237,987 Most Valuable Professional on at

Like (0)

Report

Note that it's the correct behaviour - fields returned from the query and fields used in the WHERE clause are two separate things. For example, you may want to filter customers by customer group, although you don't need customer group in the resultset.

Was this reply helpful? Yes No
psined on at

Like (0)

Report

Yeah, I realize that, totally agree. This makes the form totally developer friendly. But on another hand, from a typical business end-user perspective, nobody needs to see things like TableId or RecId or relational keys and such...

Was this reply helpful? Yes No
Martin Dráb 237,987 Most Valuable Professional on at

Like (0)

Report

Consider creating a view with just those fields you want.

Was this reply helpful? Yes No
psined on at

Like (0)

Report

The best solution would be to designate a special field group on a table, then pass that group id/name to the query object, so the query builder form could discover which fields end-users can select for building ranges. In many cases this would make sense - clean and short list, no duplicates, less error-prone, end-user friendly. Sounds like an improvement request for MSFT...

Was this reply helpful? Yes No
psined on at

Like (0)

Report

Oh, I haven't thought about views.. that's a good tip, I'll look into it. Thanks Martin

Was this reply helpful? Yes No
psined on at

Like (0)

Report

Tried views... There is big challenge - RecId in the view is not returned in X++ the same as in the underlying table, so auto relations don't work..

Was this reply helpful? Yes No