1 of 1 people found this helpful
Is your layout based on entry?
Where is the data for "other specifications" found? In the same Values table?
What specific problem do you have when you try to add the 4th value list to select Other Specifications once category, type and brand have been selected?
From what I see, you just need one more occurrence of the values table to enable the last hierarchical value list.
For those reading along, the hierarchical value lists shown here match an example found in:
There are also several other examples of hierarchical conditional value lists in this file. Each is different either in implementation and/or behavior.
Yes. You are right; I had a mistake in my value list specifications, now is working...
But I can't find a way to make work the fields in a portal... how can I do that?
You will need to explain what you mean by:
I can't find a way to make work the fields in a portal...
How is it currently "not working"?
I can't add new rows.
On my layout my table is Entry and I tried to make work the portal with related records from all the values table ocurrances. I only see different number of rows depending on the ocurrance I choose, but I can't add new rows.
That doesn't sound like a problem with your value list, but with your portal.
There are two ways to add a new row to a portal:
1) Enable "allow creation..." for the portal's table occurrence in the relationship linking the layout's table occurrence to the portal's. This puts a blank "add row" after the last actual record in your portal where you can select/enter data into the row's fields in order to create a new related record in the portal's table.
2) Use a script to add the new record. The script uses one of several means to create a new record in the portal's table with a match field set linking it to the current record on the layout. You click a button to make a new record appear in the portal, then start entering/selecting data in the fields.
Neither of these has anything to do with how your conditional value lists are set up.
If you are using 1) or 2) to add a new record, but then can't select values in your CVL formatted fields, you'll need to describe your design in much more detail.
I made it work changing my table on my layout, which now is the input information table (my prices table from which values will be chosen) and then mi portal is related with Elections table, which has the meeting specifications based on my input information.
1) General data
a. Meeting name / b. meeting place / c. date / d. Donor / e. Total price
2) Input information
a. Category / b. Type / c. Brand / d. Other specifications / e. Presentation / f. price / g. number of people
a. Category (options from input)
b. Type (options from category selection)
c. Brand (options from type selection)
d. Other specifications (options from brand selection)
e. Number of people
f. Number of products
This portal works great until I make changes in my Input information fields. After any change on that table, my portal goes blank, the information entered before disappears from the portal.
One thing that you haven't posted here are your relationships. What you describe appears to be expected behavior if the information fields are used as match fields in the relationship used as the basis for your portal.
And which table occurrence (box) is the basis for your layout?
Which is the basis for your portal?
For my layout is INPUT (original)
And for my portal is ELECCIONES
1 of 1 people found this helpful
Then any change to the value of Input::categoria will change what records appear in your portal to elecciones. This may not be what you want, but it's what you have designed your system to do.
I do not know if you have seen my file on conditional value lists, but if you compare the first Hierarchical Conditional Value List example to what you have, you'll spot a key and in fact critical difference:
The layout's table occurrence would be in the position occupied by elecciones not input.
Thus, you may need to rethink your relationships.
Working now. Thanks!