New Field Type: JSON

would like to pass the “speakers” from fireflies (like e-mails) as json (array) to fibery and then run some automations (with rules), as example: to identify the fibery users which are existing for this e-mails and link them to a multi select field in fibery.

The use case in most parts is to have automations working with the json data and enrich fibery datasets with it :slight_smile:

2 Likes

We’ll think about making JSON a proper field

4 Likes

Added support for json fields. Should be available starting from 0.1.8 node’s version

6 Likes

I love JSON. Don’t know how it’ll be used, but I’d find a way!

{
  "people": [
    { "name": "Derulo" },
    { "name": "Statham" },
    { "name": "Moama" }
  ]
}

@AdVhPkgKad @DominikM as somebody who has heavily used pseudo-JSON fields in Podio (Formula fields using javascript JSON.stringify and JSON.decode to convert hidden text fields into JSON) for over a decade, I have a question for you:

In Fibery, since its formulas do not use javascript, would JSON fields not be limited to use in automations only?

I ask, because in Podio, formula/calculation fields use javascript (though the outdated ES5), which gives immense power to JSON fields, for example we encode records otherwise not able to be looked up without tens of extra intermediary fields, and pass them on across multi-hop relationships to be used in related records in other tables/databases/apps. That said, many of these things can be done in Fibery without the need for my old hacks :partying_face:, though of course I would love javascript inside the formula fields!

@Sev We also used this Method in Podio back in the day, before we noticed, that Fibery is a better option. In my new Company, we startet from scratch with Fibery.
Currently we do not see this need for a JSON field in Fibery, since the Relationships are also way better than in Podio and the API gives us the needed freedom for all the rest.
So Hi to another old Podio Poweruser! :grinning_face_with_smiling_eyes:

3 Likes

Would be cool if the JSON field could also be used for GeoJSON, then you can easily put it on the map as points, lines and polygons.

See:

(draw some features using the menu on the top-right of the map, see how the geojson looks)

6 Likes

I would love the GeoJSON, could make things faster for the maps that I created :grin: the Latitude and Longitude can’t plot my point on the Map View

Hello @Bachi2k! nice to meet you, too. I agree 100%. We are also remodelling the data fully before importing it into Fibery, though I must say I miss the markdown display, and of course JS inside formulas!

Thankfully, for you it is in the past, but we are still in the process of migrating. Remember the maximum depth of 10 calculations?! Haha.

Awesome, we use Json a lot and this can help with config files etc.

I vouch for the GeoJson request. Its amazing for our data-visualizations.

Related / the same:

Have you created a feature request? :wink:

1 Like

Haha I think I try to self-limit my map propaganda! :grin:

(my strategy now is to try to get in a few dozen customers and encourage them to ask about maps :grinning_face_with_smiling_eyes:)

((do not worry I will build in the map features I may need myself in some way for my customers via the API and outside scripts/applications :stuck_out_tongue: I want Fibery to stay good in the main thing they do that is the core for all and not distract them. But if I notice patterns in my customers need and if I have ideas on smart & easy map features (in my estimation) that really add value then I will do a feature request. ))

2 Likes

Why not just focusing on the clients that need maps in the daily work without the need to encouraging them? (let’s keep our convo off this topic)

1 Like

2 posts were split to a new topic: New Field: Code