There are two ways of creating custom lookups. I'll show the easiest here, and maybe show the other way in the future.
So if you're thinking you'll have to create a new form and all that, forget it, you won't. All you have to do is write some pieces of code.
First let's create our lookup method directly on the table. You can check other tables for these special lookup methods. They appear in lots of tables. Take for example the table ContactPerson. It has the following custom lookup methods by default:
- lookupActionContactPerson
- lookupCustContactPerson
- lookupDirContactPerson
- lookupDirContactPersionId
- lookupVendContactPerson
Now, to create a custom lookup, we'll use the class SysTableLookup as it provides us a set of methods to do so.
Here's our method, to be created directly on the table DummyTable, with some dummy data and names.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
| public client static void lookupDummyTable(FormStringControl _ctrl, MyFilterEDT _filter){ // Intantiantes a SysTableLookup object telling it which control activated the lookup, and // what table should be displayed inside the lookup form. SysTableLookup sysTableLookup = SysTableLookup::newParameters(tablenum(DummyTable), _ctrl); Query query = new Query(); // This query will be used by the lookup form. QueryBuildDataSource qbds; ; // The "addLookupField" method adds the the fields that will be shown inside the lookup's grid. // The second, boolean parameter indicates that this field will be returned from the lookup when a // record is selected. In this case, we'll return our DummyPK. sysTableLookup.addLookupField(fieldnum(DummyTable, DummyPK), true); sysTableLookup.addLookupField(fieldnum(DummyTable, Field1)); sysTableLookup.addLookupField(fieldnum(DummyTable, Field2)); sysTableLookup.addLookupField(fieldnum(DummyTable, Field3)); // Using our dummy table as a DataSource Table. qbds = query.addDataSource(tablenum(DummyTable)); // This is the key part, what we want to filter to be displayed in the grid. qbds.addRange(fieldnum(DummyTable, MyFilterColumn)).value(_filter); // Passes the query to the sysTableLookup. sysTableLookup.parmQuery(query); // Activates the lookup. sysTableLookup.performFormLookup();} |
With that little piece of code, Dynamics AX will already display a lookup form with the table you've specified as a DataSource, displaying the fields you specified with the method addLookupField and following the results criteria of the Query you've passed to it.
Now all we have to do is actually call our lookup method, by overriding the lookup of the correct field in our Form's Data Source:
1
2
3
4
5
6
| public void lookup(FormControl _formControl, str _filterStr){ ; DummyTable::lookupDummyTable(_formControl, "SomeFilter");} |
And that's it! The lookup will be performed. But there's one additional step we'll have to take here...
When the user tries to select our DummyTable reference, Dynamics AX will display the results of the query, based on the filter we've created. So the user will only be able to see what we want him to see, and so he'll only be able to select what we want. The problem is that if he types in an existing record for the DummyTable in the control, even if does not get shown in our lookup, Dynamics AX will accept that. Remember: we're only limiting what the user may see and select for that field, but we're not limiting what he can actually type in the control. So if we don't validate it somehow, Dynamics AX will run the standard validation, which will only check if a record exists for that EDT and so on. To avoid that the user does in fact type in something we don't want, we'll have to override the validate method for our field in our Data Source. The simplest logic is to check if the DummyTable record the user typed in does attend the filter we've specified:
1
2
3
4
5
6
7
8
9
10
11
| public boolean validate(){ DummyTable dummyTable; ; dummyTable = DummyTable::find(currentRecord.DummyTableRefField); return dummyTable.MyFilterColumn == "SomeFilter"; } |
So if the user simply types in for a record that does not attend our filter, Dynamics AX won't let the user save that value.
This is the easiest way to effectively implement a custom lookup and validate the user input in case he doesn't select the record from the lookup. For this example I used a literal filter, a string. But in most cases, you'll have to filter according to what the user selected for another field in your form. Things should usually be dynamic.
Hope this helps...
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.