Hello Joao,
This column is directly handled by the system when a golden for a fuzzy entity is authored in the UI (through the SA table).
Hence why it is not present in the documentation on how to integrate the hub, as integrating fuzzy entities is done through the SD table.
That being said I understand your point, that this field is mandatory, when processing a record in SA for a fuzzy entity.
And as we provide a procedure that is working around the native behavior, then we should mention it there.
I've taken note of this point which is added to our backlog, we will make sure to update the article to take this into account.
Thank you very much for your precious feedback, it helps us provide better assistance.
Have a good day.
Alexia
Joao ROSEIRABORGES
I found this article - Update a Single Column without Going Through the Validation/Certification Checks - very helpful ffor an update I was trying to execute on Golden table for a fuzzy macthing entity.
It just lacks mentioning the column B_AUTHORINGTYPE described in this this documentation page . At least, for my use-case, I found that I needed to feed that column with the value 'OVERRIDE'.
I find it surprising that neither the doc page Publish data using SQL :: Semarchy xDM Documentation, nor the above mentioned Knowledge Base article - Update a Single Column without Going Through the Validation/Certification Checks - mentions this column as essential. Why is that? Is there some scenario for Authoring Data Publishing where we don't need to feed this column with one of the possible choices: OVERRIDE / DATA_ENTRY ?