All true. Not much to be done until it's made part of the UI overhaul.
Yep - we experience all of this. When asking support about the empty right pane, their response was it was my ISP - in that I have to give it more time for the data to come down from Marketo. I just need to give it time. Well, that was not the issue. You can keep the editor screen open for hours and it will never populate. The only solution I've found is to keep opening/closing and finally the fields render.
Have the same intermittent issue. Logging out / logging back in seems to fix it more or less.
Also, beware when this bug occurs- if someone accidentally saves whilst the 'standard objects' are showing; it will uncheck the fields that were selected and you can't fix it until it starts to work properly!
1 of 1 people found this helpful
I've found a couple things can help with this:
- Non-populating right pane - CTRL+SHIFT+R to hard refresh your Marketo window. I've found this can resolve the issue (as well as endless spinning in the navigation pane throughout the rest of Marketo)
- When you open up a token, there's a 3-5 second delay when the script window appears, and when the right pane "refreshes." In my experience, if you start to edit the code in the main window before that refresh happens, you'll end up with dropped integrations, unsaved code changes, etc. If you wait the 3-5 seconds once the pane opens until you start making updates, I've never once encountered that issue. It's only when I dive right into making changes too quickly.
- All of this has lead me to work mostly offline with my scripts. I use Notepad++ with a custom Velocity syntax highlight that Courtney Grimes put together. It mimics the look of the velocity script editors
We definitely all experience these problems, but mostly I've found slowing down at the start, hard refreshes when needed, and working offline for major edits to be my personal preferred workflow.
Best of luck!
Kind of surprised y'all are still running VTL only in Marketo (even if authoring offline)!
Recommend building your own runtime environment, which... ***spoiler alert***... is how I get big VTL projects done.
Nevertheless, you always need to verify your code in Marketo itself after testing locally, since it has some head-spinning differences from a vanilla install.
P.S. IntelliJ IDEA has built-in support (in fact uses VTL internally) and its VCS integration is seamless. Pays for itself.