@Alpha Veterans Sending automated emails in code requires this other API: https://www.wix.com/corvid/reference/wix-crm.html#emailContact I think there's an example up top

I added some comments to the original post to explain what each part of the code does!

First, when you're checking if an element has .expand, it's going to be true always. You're basically checking whether it has the capacity to expand, not whether it is expanded. You can use the not syntax to check that the element is not .collapsed : if (!$w('#id").collapsed) Not sure which one is meant to be your submit button, but it might be better to use code to ensure submit. Also, because I'm having an OCD spike, here's a much neater way of writing your code :) const elems_to_collapse = [ 'wixForms1', 'social', 'therapeute', //add as needed ], elems_to_expand = [ 'textdress', 'textsalon', //add as needed ]; export function submit_click() { Promise.all([ //Promise.all ensures an array [] of actions are completed elems_to_collapse.forEach(el => { if (!$w(`#${el}`).collapsed) $w(`#${el}`).collapse(); }), //action 1 is to collapse elements_to_collapse elems_to_expand.forEach(el => { if ($w(`#${el}`).collapsed) $w(`#${el}`).expand(); }), //action 2 is to expand elements_to_expand $w('#dataset').save() //action 3 is to save the data in the form's dataset ]).then(() => console.log("saved")) //if it works, console will print "saved" .catch(e => console.error(e)); //if it doesn't, console will display the error }

Try wrapping your url string in backticks ` ` instead of quotes ' '.

@Lee Gotcha. Yeah, trying to wrap my head around potential security holes that way but I don't think it's anything any normal iframe setup wouldn't also have. Might be a good idea to define your iiframe's sandboxing settings jic.

When you try console.log(results.items) or console.log(typeof results.items) instead, what do you see in console?

Well you have to declare event as your callback variable in the first place, or else event won't exist/be undefined: $w('#table1').onRowSelect(event => { event.preventDefault(); }); If this doesn't work and your table has no overflow, you might also try getting the current Y scroll using wixWindow.getBoundingRect and returning to it immediately instead.

You might try using event.preventDefault()

@vicihealthco Sure. For most purposes a router would be noticeably faster. The delay is probably partly due to module load order, and I'm guessing since the data is delivered alongside the HTTP request it can load before these modules intervene.

@Lee It's not meant to be a secret or anything. In fact, it's the recommended way and even highlighted in a few official examples. The docs highlight the basic principle because you can do just about whatever you want with it. Just use the $w object selector to relay messages and the rest is up to you. You can use window.parent.postMessage("", "*") from the iframe.

This is outdated/deprecated Corvid syntax. Try one of these two: https://www.wix.com/corvid/reference/$w.Repeater.html#onItemReady https://www.wix.com/corvid/reference/$w.Repeater.html#forEachItem

Input objects have both a placeholder and value property so try setting them both.

If you want a new feature, please post in the feature request section.

@vicihealthco Although you are fetching the data and delivering it with code, that does not mean you are connecting it with code. If you use the onItemReady property of a repeater you can connect it with Corvid directly and thus control the loading behavior. Bear in mind, even if you are using a backend function to deliver data that does not guarantee a faster load time like a router would.

In that case, is your lightbox set up in such a way that you can change its position?

@Logan Eldridge That looks good to me. Make sure to check the API docs to see if something is a promise or if it has a callback. The linter may or may not be consistent on this, so that's the better option. Also, if you needed to, you could either create your own promise for setfieldvalues or use async await.

Make sure your collection's main field is not empty. Contact Wix Support if you have any issues with this, as your question is not related to Corvid.

@Logan Eldridge No, you don't. The proper way is to wait until the dataset is ready to add your event listener, not to add an onready inside of the event listener itself.

This is not a forum for complaints, if you're interested in a solution, I suggest you reformat and make a new post to have something to do with Corvid.

The problem is the onReady event only fires once on dataset load, and it's not a promise - it's only a void callback. You can add event listeners that will fire inside of it for as long as the page is active, but it only happens once. So: $w('#dataset').onReady(() => { promise1().then(r => { promise2().then(res => { }).catch(err => console.error(err)); }).catch(e => console.error(e)); });