Question:
Why put a feature out with a mystery syntax? I’ve uncovered you need this options = {"fields’ : } I’ve tried about 12 different ways to get this idiotic array to work but nope - nada. {key: “var”},…, {fieldKey: and so on. Why do you do this?
Product:
Duh? Studio
What are you trying to achieve:
[Explain the details of what you are trying to achieve. The more details you provide, the easier it is to understand what you need.]
What have you already tried:
[Share resources, forum topics, articles, or tutorials you’ve already used to try and answer your question.]
Additional information:
[Include any other pertinent details or information that might be helpful for people to know when trying to answer your question.]
did you ever solve this? I have a similar issue. I am trying to use the options for wixeventsv2 getEvent() which are said to be an object which is an array of requested fields…
I wound up using a events.js listener to get the Event from a prior step. I was able to parse out the information I needed and stored it locally. Not elegant, but works. Sorry, I didn’t see this, and I hope you solved your issue. I have so given up on getting anything terribly useful from these forums.
You know its a Wix bug that they don’t want to discuss if you get radio silence. It’s usually these overlooked areas where poor quality control allowed sloppy execution to sneak in. To be fair, it’s not everywhere, but unfortunately, it is fairly common within the new code packages where you need the most help.
One other trick I didn’t try that might work is to do the following. Also not in the docs, but you can access the ENUMs by attaching the highlighted text as follows
type: .ENUM
That’s worked in other cases, but never went back to see if it work on EventsV2.
Hope this helps,
-Brian
Thank you. I will keep trying.
