Hi, I’m trying to get a component’s name and insert it as a class name. A google search tells me I should use this.constructor.name, but that doesn’t seem to work here.
Eg:
function OrderLineItems(props) {
return (
<section className={thi...
Hi, I could use some advice on the following use case. One base, four tables:
ProductsOrdersOrder Line ItemsOut of Stock Products
Orders are linked to its Order Line Items, and each Order Line Item record is linked to 1 Product record from the Produc...
I’m working on a rather bulky script, and because I’m trying to keep it clean I try and create functions for repetitive tasks. But it seems that using functions inside the scripting block also results in a poor logging behaviour in the output screen....
I’m creating a WordPress catalog site, of which the products are stored in an Airtable database. This base remains the core of all our products, and with the use of a custom import script I’m pulling in the right data from Airtable to WordPress.
Now ...
I’m about to develop a public view of our entire product database, which is one Airtable base of around 2000 records. Right now we’re having something like that in place, but basically just as an embedded view (the standard Airtable functionality) – ...
As you explain that, it’s indeed doable but a total hassle. I’m more and more skewing towards “hard pasting” the product data into the Order Line Items instead using linked lookup data
This “hard pasting” has other benefits which I hadn’t thought of ...
Just create a new record for the product in your “out of stock” table with all the same information from the original product table — including all the data from your linked record field. That will relink the product to all of the orders that are as...
Hmm, how open are you to the idea of putting the data you’re looking up from the Product record directly into the Order Line Items record instead?
That is to say, no more lookups, just paste that data in every time
Hmm, actually, that is a very int...
Try getting the current value of that record’s checkbox field and just inverse it using !.
Something like this (untested code):
await table.updateRecordAsync(recordId, {
"Interest" : ! record.getCellValue("Interest"),
})
Yeah, not moving them into an Out of Stock table and just using views would be the easiest way. But for some reasons that actually isn’t advisable for us at this time, so not really taking it as an option at the moment. Sadly enough. Thanks though!