Hello community…
I guess I am used to Podio logic…
Before we have 3 apps. A (orders), B (new line), C (line items).
In app A is relation to B where every time we create new line item.
In app B first field is relation to app C, than in B we just type quantity and price.
So when I click new item from A to B everything is ok.
But if we need new item in app C (new line items) and we click save and return back to app B it goes straight back to app A where related field is now selected. But then when I refresh app A, related field is empty again.
Hope this make sense. Is there a better way or what am I missing?
1 Like
Hi @tomaz,
first of all, a warm welcome to the Tape community. Thanks for being part of it!
This sounds like a bug to me, I’m in the middle of recreating your scenario to reproduce the issue to understand the problem better.
I’ll get back to you later today as soon as I have more specific understanding. And many thanks for the report.
Cheers
Leo
1 Like
@tomaz, I tried to reproduce your behavior and rebuilt your scenario, but unfortunately could not reproduce your issue.
With this link you can duplicate my recreation in your organization.
Could you tell me where I deviate, or maybe send me a video via message so I can understand the problem better?
Best
Leo
Thanks for such a quick response.
Will try yours first thing in the morning and will let you know. 
1 Like
Morning @Leo, I used your template… Everything works as it should.
So in app A where the field is related to app B you have not used any view. In this case users can direct select already made items in app B with already used prices and quantity.
I have set up new view in app B with filter “tomorrow”. This way every time users will create new lines than select the right line, type new price and new quantity.
Morning @tomaz, great to hear it is now working as it should.
Please contact us at any time if you have any questions or if something is not working as it should.
Cheers
Leo
@Leo your setup is working, but mine is not.
I have set up new view in app B with filter “tomorrow”. This way every time users will create new lines than select the right line, type new price and new quantity. In this case item is saved to relation field in app A, after refresh nothing is related.
I’m really sorry @tomaz! I misunderstood you in your post, I’ll reproduce your case exactly with the filter, check what the issue is and get back to you!
1 Like
@tomaz I think finally I understood the root cause of the problem. After you restrict the relation field to the view with the filter “tomorrow” the relation field only allows records to be related that match this filter condition.
After you go over the client returns the record and it is set in the relation field (without any server check), but you can’t save the Order in App A or on refresh the entry is missing because the server throws an error because the condition “tomorrow” is violated (I verified this via the console). The behavior of the server is actually correct, apparently Podio was more tolerant in enforcing this condition and that’s why the case worked.
I will discuss the issue in the team and provide you a solution.
Cheers
Leo
@Leo that makes a lot of sense. Thank you for taking the time and effort.
So in Podio was option filter “next year”. In Tape the most future filter that I found is “tomorrow”.
Did I miss anything or how can I reproduce this kind of setup?
1 Like
@tomaz have just decided in the product team to disable the server check in the web client for the view filter on relations to enable your use case. Everything else would have been workarounds with the automations.
I’ll let you know when we have the change live and you can implement your use case as usual.
Cheers
Leo
@tomaz, the update is live. Have disabled the server check for the web client. 
Can you please check again if your use case now works as expected?
Cheers
Leo
Only mobile and tablet until monday morning.
Will check first thing in the morning and will let you know.
Much appreciated. Have a great weekend.
1 Like
I could not resist so I tried it on ipad and it works.
Thanks again. 
2 Likes
