Objects not seen in queries until object is resaved

kklosson

Here's the gist:

I create a child object from it's parent's form - all good.
In other queries, the object does not appear as it should - all bad.
Open child object, change nothing, and save, and object appears in queries - all weird.

Here's a 5 min video to demonstrate...
http://vimeo.com/92285021

hpl123

Have you tried experimenting with different ways of adding the child object e.g. process CREATE, ENTER NEW etc.?

customaware

Hi Kingsley.

In your video I noticed that you create the Review from the PHS screen. Once you enter the data you press Create button. The popup closes and then you are back at the PHS screen.

You then click the Close button on the PHS screen.

What happens if at that point you click the Save button rather than the Close button?

Please try it and let us know.

kklosson

Thanks for watching. I did try that and it made no difference.

UPDATE: I was using one form for create and another for edit. The create form lacked a couple of attributes that were not necessary at the creation. I changed it so that the Edit form was used for both actions and this seemed to resolve it. I do not understand why. I am contemplating deleting the old create form and recreating it just to see the result.

Rennur

In your rules, you create reviews for Investigators. Are you logged in as investigator if not, they might be filtered out?
Maybe check your Review query filter options against LoggedIn access level.

kklosson

I am logged in as Investigator and as you saw, the query worked perfectly after opening and saving the review object, I was logged in under the same account the whole time.

ACDC

I once had a similar problem and the cause was the "owned by" relationship was being violated by a change I had made. Have you checked your relation shio setup on other referred objects and with recent changes

customaware

Interesting point ACDC.

I would be really interested how to do this properly.

Relationship originally created as Peer. When child created the link to the parent is created automatically. No problem.

Then, later realise later that needed to have the relationship Owned By. Cannot change the original. Hence create a new Owned By Attribute. Run a process to assign all the original attributes to the new Owned By hence in the future ignoring the Peer link.

However, The Peer link is the only one that continues to automatically get created when a child is created. I have to manually in a rule assign the child to the Owned By attribute.

Would be nice to somehow tell aware to ignore the Peer and automatically create the Owned By.

Am I missing something obvious?

ACDC

If you create a child object from the owner object then it will automatically attach itself to the object, but if you create the child object from a separate process and not from the form of the owner object, then it does not know where to assign it. So either a rule on the child object to attach it or a rule in the process to attach is needed - (I prefer using rules on the object to do this kind of action)

Also if you change a relationships by switching existing references from Multiple to Single there are consequences - Its best to create a new attribute from fresh. I suspect the problem with KKlosson post has got something to do with this. Somewhere there is a single/multiple conflict lurking brought on by a switch in relationship of references on the object

ACDC

Kklosson

I suspect the problem has got something to do with a single/multiple conflict lurking brought on by a switch in relationship of references on the object