Question

System.owner refers to a non-existing object

1

Hi, I get the following error in the console and am looking for a resolution... how can I change the association between my screening object and an owner? I tried using a Microflow but it seems this doesn't allow me to set the owner relation? The association 'System.owner' of object 'Screening.Screening' with data store id '915' refers to a non-existing object 'Support.ClientUser' with data store id '721'.

asked 2012-05-29

Han Pieter Duyverman

4 answers

David Sanders · Answer 1 · 2012-05-29

I'm not sure I understand what you're asking... System.owner is a relationship maintained by the system automatically which records which user created an object. I do not believe you can amend the content of this through a microflow.

Instead, if you need to be able to set an 'owner' of an record, create your own association between your object and account object, then you should be able to maintain it through microflows as you wish.

Sebastiaan van den Broek · Answer 2 · 2012-05-30

You cannot set the System.owner yourself. It is possible that the user that was originally the owner of an object was deleted. We do not clear System.owner references when a user is deleted because this would result in a huge amount of queries slowing the system significantly. The edge case where a System.owner no longer has an attached user is something you will have to take into account, the warning you showed is a result of that.

Lex van Rooy · Answer 3 · 2012-05-29

I suggest you update your question with some image to give everyone a better grasp of the situation....

But in general - you create a new object with a buttonaction from a datagrid that contains the relation with the parent. Which makes the connection automaticly.

OR

you go through a workflow that EITHER was the parent object as an input parameter OR that retrieves the parent object via an Action. Then after creating an new Screening object your next action is a CHANGE, and there you define the relation with the parent object, and commit.

Bart Tolen · Answer 4 · 2012-05-30

If you delete a System.User (or an inherited Account) then all objects that have this user as their owner can give an error saying non-existing object.

A solution is not to delete but inactivate users.

And fixing the current issue can only be done in the database if you know what you are doing by changing userid 721 to an existing user id.