fbpx

Reply To: Filter list

Forums Designer Building applications Filter list Reply To: Filter list

    triggre
    Keymaster

    Hello Alex,

    Allow me to answer your question as Jochem is tied up at the moment.

    I assume your screenshot is from a table filter and you selected drives to be shown in the table: the filter rule is seen as invalid, because it expects a True/False rule, which can be tested against each drive record to determine whether is should be shown in the table or not. Your current rule has a list as outcome. I think what you want is possible, but requires some actions, instead of just a simple table filter. Here’s how I would do it:

    If I understand your case correctly, you want a page for a request with a table of drives which are not in the request on the left side. You didn’t mention it explicitly, but I’ll assume that if a drive has been selected for the request it goes to a table on the right side of the page. Also, there are three data items involved: Drive, Request and an intermediate item called RequestDrives. Each RequestDrives has a reference to one Drive and one Request (while both Drive and Request can reference multiple RequestDrives).

    You likely have a button which the user can click to add a new request. After that button, I would add:
    1. A flow part which creates a new request (such as the default Create Request flow part, or a custom flow part, as long as it has the request as output).
    2. A flow part called Get Drives. This flow part would take the newly added request from the previous flow part as input and would contain three actions:
    2-1: A look-up action for all drives.
    2-2: A look-up for all drives currently attached to the request. You can do this by using the List contains-function and would look like: List Inputs / Request / RequestDrives / Drive Contains Drive.
    2-3: A calculation action with the Remove function that removes the drives found in action 2-2 from all the drives found in action 2-1. These are all the drives not yet attached to the request.
    This flow part then has a list of drives attached to the request (looked up in action 2-2) and a list of drives not attached to the request (determined by action 2-3 as output).
    3. A page with two tables, which both show data from the user flow. On the left side you show the drives not attached to the request (from the previous flow part) and on the right side you show the drives that are attached to the request (also from the previous flow part). This page would also have a button that applies to records shown on the left side.
    4. Next comes the Create RequestDrives flow part, which takes the request from Step 1 and the selected drive from Step 3 as input. Make sure to hook this flow part up to Get Drives flow part (Step 2).

    Will that solve your case? If any part of my explanation is not clear, please let me know and I can send you an example.

Get a free trial to discover what Triggre has to offer!

By signing up for your personalized walkthrough, you agree to receive e-mails from Triggre.