non-revisioned properties or xProperties on an item

Hi,

there is no easy way, but tons of options.

1. Maybe this community project works for you, but I haven´t tested it much: github.com/.../lc-based-props-and-fields

2. Simply solution for a very very small number of properties: Add a custom button to a certain element (like the description textarea), open a script prompt to get the user input, than edit the item with grant permission or SQL. This one does also work well from grid!

3. Build a custom Form that uses the same ItemType but use this one with low priority index. Reuse the properties you want to have editable. Call the secondary Form inside your main Form and edit the main item according to the user input.
Example:

This variant can also be extended to be more generic to work across multiple ItemTypes.

For Option 2 and 3 Form call and editing are pretty simple if you are a bit familiar with the basic AML calls. Not simple is to make it all work flawless, cause you can easily create "dirty" DOM items which leads to error messages from Innovator caused by improper editing. So expect a lot of testing. 

Hi,

there is no easy way, but tons of options.

1. Maybe this community project works for you, but I haven´t tested it much: github.com/.../lc-based-props-and-fields

2. Simply solution for a very very small number of properties: Add a custom button to a certain element (like the description textarea), open a script prompt to get the user input, than edit the item with grant permission or SQL. This one does also work well from grid!

3. Build a custom Form that uses the same ItemType but use this one with low priority index. Reuse the properties you want to have editable. Call the secondary Form inside your main Form and edit the main item according to the user input.
Example:

This variant can also be extended to be more generic to work across multiple ItemTypes.

For Option 2 and 3 Form call and editing are pretty simple if you are a bit familiar with the basic AML calls. Not simple is to make it all work flawless, cause you can easily create "dirty" DOM items which leads to error messages from Innovator caused by improper editing. So expect a lot of testing.