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

Clarify storing of object references

Description

We need to clarify the storing of object references:

A reference to another object is stored as integer:

 

If the reference is null, we store an empty string:

 

Does this behavior make sense? Do we handle the following situations in all parts of DATAGERRY (WebUI, Exportd, …):

  • a user sets a nonsense string as value via REST: “foobar“

  • a user sets the object reference as string instead of using an integer “5“ instead of 5 via REST

  • a user sets an non existing public_id as object ref

 

The yourCMDB migrator currently sets a non-existing references with the value 0, which results in the following error message:

 

Activity

Show:
Michael Batz
August 14, 2020, 1:09 PM

Discussed in refinement, we don’t need to handle that.

Assignee

Unassigned

Reporter

Michael Batz

Labels

Story Points

None

Tester

None

Priority

Medium
Configure