Skip to main content

Notifications

Announcements

No record found.

Dynamics 365 Community / Forums / Finance forum / How to manage filter c...
Finance forum
Suggested answer

How to manage filter coonstraint in sysgen lookup form

Posted on by 15

Hi all

My situation is as follows:

I have a form. In the form there is a grid In the grid there is a string field.

Addin a new line in the gid, I type in some letters and a lookup form pops up, showing possible entries. 

It filters on what I types in. Filter conditionion is "begins with"

A Sub-Form of this form has a grid, based on the same table, showing nearly the same behavior, but the lookup form has the condition "Exact match"

Additionally it seems to show a different behavior, opening it manually, or when it opens by itself because of typing letters.

So in our solution, we have many of this lookups and they don't show the same behavior, what is not OK.

So the question is: Where is the condition defined? Can we manipulate it?

followowing image shows, which condition I'm talking about.

4010.pastedimage1611316291102v1.png

thanks You for any helping answer.

kind regards

Gerhard

  • Suggested answer
    nmaenpaa Profile Picture
    nmaenpaa 101,148 on at
    RE: How to manage filter coonstraint in sysgen lookup form

    If two fields work differently, there must be some difference in them. So you must find the difference. 

    Before that, you should clear the usage data to rule out any user-config or "last selection" variables from the equation. So far you didn't tell if you tried this or not.

    You can also compare your fields to the standard fields in the system. Is one of your fields behaving differently than any field in the standard system? If yes, you are clearly doing something differently.

    So far you have shared quite vague details so I can't really offer any more detailed help. But whenever two things work differently when they should not, a good approach is to rule out explanations one by one by examining the details of the implementation. Eventually you should find what causes the difference, and then you will also know how to avoid it.

  • GG-16051420-0 Profile Picture
    GG-16051420-0 15 on at
    RE: How to manage filter coonstraint in sysgen lookup form

    I checked different string entry field, they all show a different behavior. The one from my last post changes its bahavior, the next one has always the filter option"contains" in both situations, with or without typed in something.

    Regarding to my first posting here:

    We have two similar grids, showing data from the same table, showing different behavior.

    So, if You say, it is managed  by microsoft, I'd like to know, which rules are behind it, so we can give a hint to our users, how to use the filtering function.

    Sorry for not stopping this questiuons, I'm frustrated about having no chance to get this run, as expected.

  • Suggested answer
    nmaenpaa Profile Picture
    nmaenpaa 101,148 on at
    RE: How to manage filter coonstraint in sysgen lookup form

    Ok so now the question is:

    The filtering in the lookup works a bit differently if you had typed something in the field before opening the lookup, compared to opening the lookup without typing anything. And you want to know if you can control this?

    I think that this behavior is not something that we can control, it's managed by Microsoft.

    I assume you can see similar behavior across the entire system, not just in your form / field. Correct?

  • GG-16051420-0 Profile Picture
    GG-16051420-0 15 on at
    RE: How to manage filter coonstraint in sysgen lookup form

    In my last posting I'm talking about only one field.

    Somebody figured out, there are two comparable fields with different behavior.

    I figured out, I can get different behavior in one field, when opening it in different ways, as described above.

  • Suggested answer
    nmaenpaa Profile Picture
    nmaenpaa 101,148 on at
    RE: How to manage filter coonstraint in sysgen lookup form

    Could you please clarify if the two fields are working differently or the same way?

    You told that one of the fields works a bit differently, depending if the user inputs some text or not. But are the two fields working the same way or not?

    Clearing the usage data helps you to see how the system works, when there's guaranteed to not be any details "remembered" from last time the user used the form / lookup. Here's how to clear it: www.google.com/search

  • GG-16051420-0 Profile Picture
    GG-16051420-0 15 on at
    RE: How to manage filter coonstraint in sysgen lookup form

    It is the same tablefield. The difference is only, opening by clicking or getting it opened by typing in "te".

    No, I didn't try clearing usage data.

    I type in "te", the lookup opens, as shown in second screenshot.

    I delete the letters, using backspace and close the lookup.

    I click on the "down arrow" to reopen it, and it opens as shown in first screenshot.

    I type in "te" and it finds matching entries.

    I close and reopen it and it is back to second screenshot.

    Where Do I have to clear usage data?

    Will it help me in this situation?

  • nmaenpaa Profile Picture
    nmaenpaa 101,148 on at
    RE: How to manage filter coonstraint in sysgen lookup form

    And are there any differences in how you set up the table fields, form data source fields, form controls?

    Did you try to clear usage data?

  • GG-16051420-0 Profile Picture
    GG-16051420-0 15 on at
    RE: How to manage filter coonstraint in sysgen lookup form

    Sorry, it is named "is exactly"

    pastedimage1611319888347v1.png

    here is a screenshot of the same form, but it opened becaus I typed in "te".

  • nmaenpaa Profile Picture
    nmaenpaa 101,148 on at
    RE: How to manage filter coonstraint in sysgen lookup form

    Could you share a screenshot of the "exact match" dialog? I don't have such option at all. I have "matches" and "is exactly".

    Also all other details regarding the differences of these two fields and their definitions are welcome.

  • GG-16051420-0 Profile Picture
    GG-16051420-0 15 on at
    RE: How to manage filter coonstraint in sysgen lookup form

    thanks for answering,

    but  no, it is not remembering it.

    In the case, where it shows "exat match", when I change to "begins with", select something and reopen it, it switched back to "exact match".

    And the original state ist "exact match", but I want it to be "begins with" as default behavior

Helpful resources

Quick Links

Replay now available! Dynamics 365 Community Call (CRM Edition)

Catch up on the first D365 Community Call held on 7/10

Community Spotlight of the Month

Kudos to Saurav Dhyani!

Congratulations to the June Top 10 community leaders!

These stars go above and beyond . . .

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 288,459 Super User

#2
Martin Dráb Profile Picture

Martin Dráb 225,783 Super User

#3
nmaenpaa Profile Picture

nmaenpaa 101,148

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans