We're updating the issue view to help you get more done. 

Field references with selection of multiple types

Description

As thought at the beginning of the specifications for the type generator, we should give the possibility to give several types from reference selection for a reference field.

The type field should not contain a single value (TypeID), but rather a list of possible type IDs.

For compatibility reasons, I would suggest that these are interpreted according to the particular storage type. So we would not have to change the database structure at this point.

We also need to handle references to multiple types in Exportd/DocAPI.

Activity

Show:
Mark Heumüller
March 12, 2020, 9:53 AM

Yes, we would then have to check at which points the implementation could break the current interfaces. Sergei and I had a brief look at it. As I said, the way it looks, no database migration needs to be done. But let's move the topic to a later sprint.

Michael Batz
March 12, 2020, 10:02 AM

tagged that with “Refinement“. Lets talk about that issue tomorrow and decide, if we plan that for the next sprint.

Michael Batz
September 11, 2020, 8:21 AM

Started with testing of this functionality. When adding a new reference field to an existing type and choose a type for this reference, I got the following exception:

 

Michael Batz
September 24, 2020, 4:09 PM

I see a lot of issues with that story. Do you have time to do some enhanced testing of that functionality? If you found anything, please open a bug

Michael Batz
November 18, 2020, 10:36 AM

Changed the Jira Workflow from DATAGERRY -> DATAGERRY 2.0

Done

Assignee

Mark Heumüller

Reporter

Mark Heumüller

Labels

Story Points

8

Tester

None

Sprint

None

Fix versions

Priority

Medium
Configure