I’m used to import data from a CRM into a Coda table.
In this table I created calculated fields like lookup on another table.
My problem is that I can import more than 3000 rows and every time a row is imported the calculated fields work.
I was thinking of only importing data into my first table and adding calculated fields into a view, but if you add a column into a view it is automatically added to the main table.
Does anyone have an idea to separate imported data and calculated fields?
Thanks for your help.
Views are based of the table. So any column you add will first be added in the view. If you do not want to see the columns in the table just hide them. Table > Options>Columns and hide the calculated fields. This way you will only see the columns that you need to import on the table.
Thank you @Dhaval_Patel1
My problem is avoiding calculations during imports.
Then I would like to be able to use the imported data and add calculated fields.
I am not certain what you are looking for is possible. Whenever you “enable” the calculated column(s) Coda is going to calculate all the rows. It doesn’t matter whether it is with the initial “import”, or later.
Can you give more details about your problem?
When you “import”, what exactly are you doing? Copy/ paste? Upload via CSV pack?
Thank you for taking the time to respond and sorry for not being specific enough.
I import csv data into a table in which there are calculated fields, which are based on the imported data.
To avoid using calculation time during import, I would have liked to remove the calculated fields from this table and only make them appear in one view of it but who says view means all the fields of the linked table.
I don’t know if there is a solution that’s why I was counting on the experts.
The best method I can think of is to put the formula inside a button, so that you can control when the formula is executed.
The simplest way would be to have a button column. Then each row can be calculated (manually) on by one.
Probably not what you want for 3000 rows? You could then have a button outside the table, which uses forEach to push all the buttons. You could add a filter, if you only want to push some of the buttons,
Or you can run an automation to push the buttons, based on some trigger,
Hope that helps.
Thank you. I made it and it works.
It took about 7 minutes to calculate 4 columns on 148 records. A bit slow but it seems it’s the only solution.
How big/ complicated is the formula? Because that is VERY slow
This is the formula I put in a button :
ModifyRows(thisRow, Produits_DB.[Structure du produit], Switch(thisRow.productstructure,1,"Produit",2,"Famille"), Produits_DB.Statut, [Statut produits_DB].Filter([Code statut]=thisRow.statecode), Produits_DB.Parent, Produits_DB.Filter(productid=thisRow.parentproductid), Produits_DB.[File d'Attente], [Files d'attente_DB].Filter(queueid=thisRow.asip_filedattenteid), Produits_DB.[Sujets liés], [NN_Sujets Produits_DB].Filter(productid=thisRow.productid).Sujet.BulletedList(), Produits_DB.[Produits rattachés], Produits_DB.Filter(parentproductid=thisRow.productid).BulletedList())
This formula makes lookup to help users to understand id codes. Example : statecode value changed to a text label.
And it also created some lookup to show all the products inside a same family.
I am also very interested in this type of workflow. Mine might be a little different.
I want to be able to import limited data about products from an ERP. I want to be able to regularly refresh that core data from a csv.
But I want to use Coda as a simple product information management system. I want to create new tables that reference the SKU from the master data imported from the ERP. But when I create a link to the ERP table, it’s going to add additional columns that link back to the new table of extended attributes and I’m afraid refreshing the core ERP data will break the links.
Can you please provide some more details?
When you “refresh”, what does that mean? C&P? Upload?
Without details about these links, it is not possible to respond. Are these relation columns? Formula columns? Columns populated by button?
Here is a link to analysing slow formulas:
At this point I haven’t tried refreshing the data for fear of breaking it. In the simplest form, I think these are just relation columns. Formulas would be in the Extended Attributes table.
I would like to use upload to refresh the data and not copy/paste a few thousand products.
ERP Product table (imported):
SKU, Title, Price, etc., Product Attributes Relation
Product Extended Attributes:
SKU (relation), Title (lookup), Product Description, Related Products (relation to multiple SKUs), etc.
I used the “debug performance” tool.
It seems the tool stop before the end of calculation :
When I have a calculation time of 4 minutes 58 seconds.
Unfortunately I have no experience wit this tool.
Hopefully one of the other community members may be able to provide some insights.
Anyway, thanks for looking at my post.
Is it possible to share an (anonymised) doc? It is very difficult to understand like thhis.