Formula Editor Error

#1

Hi,

I’m consuming an API endpoint which returns data in this format:

{
  data: {
  },
 included: [
    {
      id: "1"
      type: "photos",
      attributes: {
        owner_id: 1,
        // other attributes
      }
    },
   {
     id: "1"
     type: "users",
     attributes: {
       email: "test_user@example.com"
     }
   }
  ]
}

I’m saving the above response in a data variable named “timeline_data”.
I’m now trying to show a list of type “photos” based on the array of objects “timeline_data.included”.

When I try to fetch the “username” using the following formula for each repeated photos, it does not work.

PICK_ITEM(SELECT(data.timeline_data.included, (item.type == "users") && (STRING(current.attributes.owner_id) == item.id)), 0).attributes.email

formula_error
formula_error1357×706 60.6 KB

formula_editor_error
formula_editor_error1357×702 71.3 KB

#2

You’re right that it’s a bit illogical that that doesn’t work. However, you can use the LOOKUP formula to access properties of objects returned as the result of another formula, so this works:

LOOKUP(LOOKUP(PICK_ITEM(SELECT(data.timeline_data.included, (item.type == "photos") && (STRING(current.attributes.owner_id) == item.id)), 0), "attributes"), "email")

(We’ve got plans on how to make long formulas more understandable too – that’s starting to be a bit painful.)

#3

In my case timeline_data.included contains objects of both users and photos type.
I think I have only one option to filter users using SELECT method in formula editor.

When I write SELECT(data.timeline_data.included, item.type == "users"), example results do not show correct data. And when I hit the “OK” button to preview my results, it also does not work as expected.

How can I filter an array of objects correctly ?

select_error
select_error1356×705 79.3 KB

#4

The examples shown in the editor need a bit more love – the results of complex formulas are not evaluated correctly into the example data; here it’s just showing that the result is “an array of objects with this schema/example data”.

The formula looks correct though – does it fail in the app itself too?

#5

Do you need consultant for assistance of “make long formulas more understandable too”?

#6

@s_p, I think we’ve got Composer Pro product design covered without external consultants, but if you’re interested in joining AppGyver as an employee, you can always send an open application to contact@appgyver.com. :slight_smile:

#7

What kind type of people you are recruiting?

Lastly working with developing / defining of business / product concepts, and not doing any kind of programming work. Is concept developer someting what appgyver is recruiting?

  1. kesäkuuta 2020, klo 13.50, “Harri Sarsa via AppGyver” <appgyver2@discoursemail.com> kirjoitti:
#8

At the moment the open positions do benefit hugely from programming expertise, but drop a line and we’ll at least keep you in mind!

Hope to get the job descriptions up somewhere soon, currently they’re available on MeetFrank.

#9

The actual formula gets little bit more complicated as I have to use this formula within a repeated component. It was not working last Friday but I’m able to get it working now.
I think may be LOOKUP did the trick.
Thank you!

1 Like