This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I have some fields that are defined as custom Enum data types and stored as the base integer in my database. For data integrity purposes, these values are mapped in the database with a foreign key to tables that define the enumeration and are used in reporting, etc.. I don't have entities in the model for these basic lookup tables, so the existence of the foreign key and the absence of the corresponding entity makes the designer want to delete my enum field when performing Update From Source. I posted a couple years ago about a similar issue with the designer hiding fields that have foreign keys. That post had some workarounds mentioned, which I can definitely still use, but if I had any feature requests for the designer this would be wayy up there.
Kris |
|
|
I am certainly not opposed to having the designer not add these FK fields by default, but if it could avoid removing valid mappings that were manually configured, <3 |
|
|
Thanks for the feedback Kris. We do have an item on the backlog to be more forgiving about the existence and non-existence of foreign keys; I've added a note to that to consider your scenario, and we'll see if we can bump it up the priority list. |
|