Thanks Bud,
I already tried that and it work for one field but the issue is to find the way to have 2 fields.
As soon as I add another with + , it display both fileds items as one item like in the second screenshot of my post.
I’ve tried :
totext(field(‘Camera’)+(field(‘Lens’))
totext(field(‘Camera’))+totext(field(‘Lens’))
Thank you for creating the general issue. We just moved from Airtable and the issue here plus not being able to link to other database tables is massively slowing down our workflow. I’ve tried every variation in this thread and then some and nothing works. Looking forward to the release where this is solved. 
I’m not sure if this is what you are trying to achieve, but maybe … ?
concat(field('Item'),' (',field('A'),') (',field('B'),') (',join(field('CompLookup'),', '),')')
This joins together some multi-selects and a lookup.
Hi @Crystal, could you please share more details about how we can improve the formula UX? Having detailed information will help us make better improvements. 
Link to a table in another database is coming soon: Link to a table in another database (#1354) · Issues · Baserow / baserow · GitLab.
And then to answer the linking databases question:
For linking other databases together at the moment, even in the enterprise edition of self hosted baserow you can sync tables (which is super cool too), but let’s say I have my affiliate team. They exist in the Affiliate database and have tables:
Affiliates (with informational fields, contact, images, etc.)
Affiliate-Assets (with a link to Affiliate Table, informational fields, images, limits, etc.)
But they just gather the data. The Affiliate Promotions are completed by the content team in the Content Matrix Database.
So the Affiliate Promotions Table (in the CM Database) needs to relate to the Affiliate Resource (In Affiliate DB) with a look up field of which affiliate it is and other related data.
Having the ability to link the Table’s primary field and additional fields and lookup fields to a non-primary field of another table in another database is what I’m expressing here.
For us this has all sort of use cases: From Data tracking and content creation to project management and documentation.
Does that help, @olgatrykush ?
I may not be the greatest candidate for describing this as I have literally zero coding skills. I’m also new here and have only worked with databases for a year so there may be other solutions.
Hi @olgatrykush yes. So overall conceptually, our first database is to store content and record the content as an asset. So for example, our blogs are all company assets filed under Blog-Assets table. Currently, there are 39 different categories of content. This includes everything from internal emails, external emails we write for partners to blogs, videos, blurbs, advice column information, website-assets, etc.
These pieces of content are all related at some point, but not always.
EXAMPLE 1: Let’s say I have an email. That email might be for a blog, a video, our newsletter, a podcast, a product announcement, etc. But at the moment, in order in order to display this information effectively and efficiently, I would want a field that would display which item the email is for. So instead of:
Legend:
| denotes field - denotes a space
Field: 1: Email ------|— Blog—|— Video—|— Newsletter—|
Row 1: Welcome1–|-------------|---------------|----HGVol.135—|
Would return:
Welcome 1, HG Vol.135
EXAMPLE 2 (and perhaps more relevant to more people):
Naming for a Table’s Primary Field
Naming an item is often a collection of their attributes. It is frequently more ideal for a primary field to be a collection of attributes assigned than having to come up with a unique name that is recognizable for the team.
So for example, if I have a Table of Blurbs (short copy paragraphs) I might want to use them in multiple places, emails, social media, blogs, etc. And a blurb typically consists of a topic, promotion, and an angle. So I might Say the topic is Carrots, to promote a garden course (Product) or a free e-guide (Digi-Paper-Asset), and talk about growing in fall for overwinter harvesting (angle).
Without the ability to have the name be a collection of attributes I have to manually name it and rely on whichever team member is writing the blurb for an accurate naming convention that matches the attributes and create redundancies or make the copy long text the name which isn’t helpful for locating data.
So:
|—Topic—|—Product—|----------Digi-Paper---------|—Angle-|
|-- Carrots|------------------|Seed to Harvest: Carrots|—Fall—|
|-- Carrots|Garden 101 |-----------------------------------|-Spring|
Would Return in the Primary Field:
Carrots, Seed to Harvest: Carrots, Fall
Carrots, Garden 101, Spring
Another instance would be for promotional calendar grid view. We have the name in Airtable as a set of attributes split up with emojis since we have a heavily visual learning team:
: EYH_2024 PACKAGE, PS 
: EYH_2024 WS EVENT 
→ → Internal, Partner 
Launch
So here we have
:
What is being promoted,
:
How it’s being promoted (Campaign),
→ →
Who is promoting it,
What type it is.
At any given time an attribute might shift. So if we decide to put a different campaign in, we can simply change out the attribute and the name will certainly be changed vs relying on manual redundancies.
