Decoding Repository Table Data

Sounds good. My only concern with "User Fields" is that they really need to have some metadata associated with each to identify at least their 'name' so that the purpose of the field doesn't get lost over time.

Using my example

Something that identifies
"User Field 1" represents "Description"
"User Field 2" represents "Allow Trigger"
"User Field 3" represents "Another Attribute #1"
"User Field 4" represents "Another Attribute #2"

And of course, the ultimate would be to also identify what type of data is permitted for the value (Boolean, Date, DateTime, String, Decimal, Integer) etc. But that turns this into a much bigger change.

How would the user interface reflect your suggestion?

What we are thinking about is adding an additional tab called "User fields" to the properties dialogue
The users then can enter anything they want.
That would require modifying the repository

ALTER TABLE OBJECTS_TREE ADD USER_FIELD_01 [nvarchar] (255) NULL
ALTER TABLE OBJECTS_TREE ADD USER_FIELD_02 [nvarchar] (255) NULL
ALTER TABLE OBJECTS_TREE ADD USER_FIELD_03 [nvarchar] (255) NULL
ALTER TABLE OBJECTS_TREE ADD USER_FIELD_04 [nvarchar] (255) NULL
ALTER TABLE OBJECTS_TREE ADD USER_FIELD_05 [nvarchar] (255) NULL
ALTER TABLE OBJECTS_TREE ADD USER_FIELD_06 [nvarchar] (255) NULL
ALTER TABLE OBJECTS_TREE ADD USER_FIELD_07 [nvarchar] (255) NULL
ALTER TABLE OBJECTS_TREE ADD USER_FIELD_08 [nvarchar] (255) NULL
ALTER TABLE OBJECTS_TREE ADD USER_FIELD_09 [nvarchar] (255) NULL
ALTER TABLE OBJECTS_TREE ADD USER_FIELD_10 [nvarchar] (255) NULL

That should not take a long time

Hi Mike. wondering if this is still on the radar?

It was partially implemented a while ago

The fields are there but you just cannot see them in the front end

Here is the link to the repository upgrade scripts

www.etl-tools.com/repository-database-up...-defined-fields.html

We have made some good progress today and we hope to have another release next week

Starting to look good. Thanks