I have experience with low and no code tools since the 80s and built a bunch myself (for niches like insurance) and eat my own dogfood by using my own no code tools for current (side and client) projects.
What I found is what everyone finds; when the tool does not support something, it gets very hard.
I think of that as follows: the request to make that 'impossible' feature came from somewhere; if you rethink the feature so it's trivial to click together with the tool and then convince the owner of the feature to accept that reality, you often get away with it. Just accepting that you don't need certain complexity for things to function well is often, imho, a perfectly fine solution.
If the client or owner does not accept to work this way, I don't use no/low code at all.
What I found is what everyone finds; when the tool does not support something, it gets very hard.
I think of that as follows: the request to make that 'impossible' feature came from somewhere; if you rethink the feature so it's trivial to click together with the tool and then convince the owner of the feature to accept that reality, you often get away with it. Just accepting that you don't need certain complexity for things to function well is often, imho, a perfectly fine solution.
If the client or owner does not accept to work this way, I don't use no/low code at all.