Widgets like datagrid2 and gallery don't support the 'listen to' feature yet, so I needed a general workaround which can also help in your scenario.
What I did is create a non-persistent helper entity with an association to the target entity (in your case, planning). The on-click action of the list view would then set the association to the target object and refresh the helper object, achieving the same effect.
The "Create" button could then create a new object and set the association to the newly created object.
Only thing you need to add is a microflow or nanoflow to open the page. This would create the help object and retrieve the first object from the list view (based on the same xpath & sort order) to ensure that you don't start with an empty right side of the page.
Does that help?