Hi Joe,Ignoring the workflow issues:On the edit page you could use something like:ERDEditStringWithChoicesI modified ERDEditStringWithChoices so that you can use a key path as well as a dictionary or array in the rules (not thoroughly tested). You may want to clone ERDEditStringWithChoices and cust
You have a bit of a workflow going on in that requirement.
- If property is null, provide selectable list of string values obtained from
an arbitrary entity.
- If property is not null allow its string value to be edited free from.
In addition you will need to handle:
- Do you need to be able to
I won't be setting a relationship to that Person type, but want to
fill in the values. I can't assume these will be set on creation
either, just if the properties are null (whether on creation of entity
or later when editing). My thinking is the modern approach is some
sort of ajax live search on t
Hi Joe.
I may have interpreted this incorrectly but I'll try some suggestions.
I don't think your issue is a D2W problem per se.
I would consider this a modelling one - if a membership is linked to a
user but you want some details copied in to the membership on
creation, then can't you do that a
Ok, I'll try to give a more specific example.
I have a Membership entity with such properties as beginDate, endDate,
company (relationship) and primaryContactName and primaryContactEmail.
The end users want to select these last two values from a pull down
list of known company.Affiliates, where Af
I want the certain fields (String) to take the values from a pull down
from another Entity, inserting Entity.name or Entity.type for the
string on selection. I don't want a relation since the choices are to
be archival and not reflect what Entity.type is presently, but what it
was at time of creati
