Sub connections missing?

Same here. And the variable $PARENT...$ is still not available.

Hi all,

Can each please post screenshots of your issue? Where is the $PARENT...$ variable not available or not substituted properly. Also what data source type?

Everything looks good on my end (see image below). I'm trying to figure out what is going on so that we can fix it. RDM v2022.3 has had a major overhaul of the Parent/Child (sub-connections) connections make sub-connections full fledge connections. The result is that we can now support things like Logs/Attachments/Documentation/... at the sub-connection but visually other than the new features available should be identical as before.

Best regards,

I have a case number: 00012655

Unfortunately, the problem was not fixed after the update.

Here are my sub-connections.

The parent entry was deleted after/from the update.

If I manually create an entry and a sub-connection, it looks like this:

Parent:

Child:

@thomas11 This is very odd. The migration steps included with v2022.3 takes the old parent/child format, extracts the children from the parent and saves them individually. The process, extract the children from the parent, save the parent and then saves each child. I'm curious understand where/how the parents got deleted during this process.

Do you have any deleted parents in the Administration > Delete Entries?

I'm thinking a remote session might be our best bet going forward here. I can get Etienne to set that up for us if you like.

Best regards,