We have process wherein the business case requires us to start a New SQL DB that will record Supplier/Customer details. These details might or might not be on our Finance system hence the requirement to keep it in a separate DB. The challenge is that business would like to have a simulated lookup field. Wherein the user can start capturing the name of the Supplier / Customer and if there are values in the DB that match, it provides them with the list of similar names. If the one they are capturing already exists, then they can select it, but if it does not, then they will type the remaining porting of the name and we can use WF to update the DB with the new details so that it is available in the future. 

The initial idea to achieve this was to setup the field as a Dynamic Field, however in the client, one is not allowed to capture a new value against the field if it does not exist in the referenced external table. Workflow however is happy to add a value to the field without it being in the table. 

I understand we could use the approach of having multiple fields or templates, but all these options force the client to fist save the data then having Workflow run a processes of checking and then reporting back to the document for them to know if the Supplier/Customer is availble or not. So it increases the time to capture and processes the document. Is there any potential for this behaviour to become a feature in a future release?