Thank you very much my friend! For me this is really a depper level of programming (forget the NO-CODE here )
And just to put my 2 cents in this discussion, following the updated version of your project that add the full path of the object (as I need to show in my project):
if you add path as a parameter to searchName and update it as you recurse, you don’t have to worry about trimming the last node off the path when you pop out of recursion at any level - it will take care of itself.
This is a simple trick to discover if the object is a bucket or a simple value (no nested objects below)… This was something I discovered empirically testing when showing in the screen the results of a cloud variable. And it works!
That’s are the things we need learn to reach the next level in APP development, and just because this community help, I’m moving forward with Thunkable.
I was trying to find a replacement of JavaScript typeof property.
I started to convert the object to JSON and count the number of colons in the JSON. Only a terminal node will contain a single colon, other nodes (buckets) will always have more than one colon.