Static List doesnt show when atttr is a reference attribute

ddumas

I have an object named Arrangement, with an arrangement attribute. I have a static list defined inside it, and the "allow other" checkbox is checked.

This attribute exists as a drop down inside a related object named Project.

When I create a Project, the drop down on the Arrangement attribute does not display the static values I had setup in the Arrangement object.

So, I am confused to the functionality of static choices, when used as part of a related object.

I was hoping that setting up the static values would serve to "seed" the Arrangement object's records, but that additional values could be created at runtime, and then be used in the dropdown in side the Project object.

Dave

aware_support

You don't need static choices inside the Arrangement object. Just have one attribute called Name without any choices. At runtime create as many instances of this object as you like. Then make sure that you display the reference to Arrangement inside Project as a drop down. Aware IM will automatically populate the drop down with values for Arrangement created at runtime.

ddumas

aware_support wrote
You don't need static choices inside the Arrangement object. Just have one attribute called Name without any choices. At runtime create as many instances of this object as you like. Then make sure that you display the reference to Arrangement inside Project as a drop down. Aware IM will automatically populate the drop down with values for Arrangement created at runtime.

I understand that I can do that, however I was hoping to seed values so that that an admin does not have to enter these "static" values each time for each installation. Does that make sense?

aware_support

Then create these values automatically in the system initialisation process:

CREATE Arrangement WITH Arrangement.Name='Name1'
CREATE Arrangement WITH Arrangement.Name='Name2'

etc

ddumas

aware_support wrote
Then create these values automatically in the system initialisation process:

CREATE Arrangement WITH Arrangement.Name='Name1'
CREATE Arrangement WITH Arrangement.Name='Name2'

etc

Perfect, I like that.