Now you can copy and paste content in Table View. There are many cases where it is helpful. You may just copy Excel table, you may copy some values and paste it to other cells. This will speed up data handling in Fibery a lot.
Collections in Lookup Fields
Now you can see Collections from Types linked by to-one relation. For example, we have Lead - Account, and inside an Account we have a list of Apps. But we want to see this list in Lead as well. Here is how you can setup it:
I found some weirdness with copy+paste. I am on Windows 10.
I can copy and paste both within the same table in Fibery and between different tables in Fibery with no problems. I can also copy single columns from Excel and paste in Fibery with no problems. BUT:
I CANNOT copy multiple columns and rows from Excel and paste in Fibery, UNLESS the paste action can add a new empty row to the table. E.g., if I copy a matrix of several columns and N rows from Excel I cannot paste it into a table in Fibery unless I select a cell that is on the Nth row from the bottom in Fibery. This also adds a new row to the table.
When i try to paste an N-row matrix that is not on the Nth row from the bottom in Fibery, the correct cell values flash briefly on the screen, but they are not actually added to the table.
There still seems to be a hickup. Let me explain a bit deeper. So maybe we can solve this.
We have a db called Customer journey â This is C
C has a many - many relation with the db âAppointmentâ â This is B â We call this field 'Afspraak' (Appointment)
In db âAppointmentâ we have a relation with the db âLeadstatusâ â This is A â We call this field 'Uitkomst call' (Outcome of the call).
Leadstatus (A) can have many Appointments (B), but an Appointment can only have one Leadstatus.
I believe this should be the other way around.
In Contact we show the entities of C â The Customer journey.
When we have a salescall we can use Leadstatus to set the outcome of the salescall. For example âSend proposalâ.
When an Appointment (B) is linked to the Customer Journey (C), I would like to show in C what the linked Leadstatus (A) in B is.
Conclusion: when I open the contact, I want to see in an instant what the outcome (A) is of the Appointment (B) in that specific step in the Customer Journey(C).
As you look at the image. The â Voorstel versturenâ (= database Leadstatus) should be shown at the blue âAfspraak ingeplandâ entity.
This is what I was searching for, where (xxx) can be left empty since we only link 1 appointment to customer journey. So why a many - many relation, I hear you thinking.
Because of the place of this relation when I open the entity. With one â right side. With many â left side.
If it were possible to choose a one-relationship database below it as a second-level database that would be great. Because we use many like them in many different places to achieve the right views.
Another example: An appointment can in fact have only 1 form, but we have now chosen a many relation. With a one relation, we cannot show a feed from the form in the appointment itself.