Skip to main content
Question

There are no compatible fields"" when creating Dynamic Form Rule

  • November 27, 2018
  • 0 replies
  • 110 views
I'm creating a form on which are several lookup fields from another table.

When a user makes a selection from the dropdown field [Name] (from another table) it looks up the value in [Type] (in the same table as [Name]) and displays that on the form as well.

What I'm trying to do using Dynamic Form Rules is say:

When [Type] is equal to X value, change [Type (Billed As)] to X value

The problem is that in setting up the first part of this for [Type] I get the message "There are no compatible fields" in [Type].

I assume the reason for this is that technically there are no values present in [Type] to compare against until something in [Name] is selected first. I don't know how to force the dynamic rule to ignore this requirement. Is there another way?
    This topic has been closed for replies.

    • JamesTrory
    • Author
    • Registered
    • November 29, 2018
    Anyone? Still could use some help with this if anyone has any ideas.
    Can you tell me what field type is [Type]
    • JamesTrory
    • Author
    • Registered
    • December 5, 2018
    It's a multi-select text field.

    I'm sure some context will help. It could be that I'm going about this all wrong.

    I'm building a photo production app. [Name] is obviously the person's name. [Type] is the job role that they typically have, eg. Photographer, Digital Tech, Stylist, etc. There is also a field called [Rate] which looks up how much they cost per day.

    Most people only have one role but some people might have two so that is why [Type] is multi-select. It also means that their [Rate] can vary.

    What I'm trying to do in the form is use [Name] as a dropdown field for a user to find someone and then it will lookup their [Type] and their [Rate]. This works fine as a basic lookup because like I said, 95% of the [Name] choices will only have one [Type] and one [Rate].

    Where it's getting overly complicated is that what if a person has two values in [Type]? How do we know which one they should get billed for and what the correct [Rate] is? This I believe requires user interaction.

    So I had the idea of introducing a new field called [Type (Billed As)] which can be selected manually by the user to effectively 'overwrite' the default [Type] value if they have to.

    Example - if the default [Type] is Digital Tech the user can say no, today they were billed as a Photographer and select that from [Type (Billed As)], overwriting the automatic selection of Digital Tech from [Type].

    Of course I'm making this very hard on myself.
    Terms & ConditionsAccessibility statement