Upsert using sObjectField displays error in editor
Issue #638
resolved
When using upsert with an external Id field the editor displays an error as attached "';' Expected, got '.'"
upsert acc Account.Name //I know not a real external Id but this is where it occurs
Comments (14)
-
repo owner
-
repo owner
My original assessment was wrong. The issue was that my parser was only allowing a simple identifier for the optional external ID in an upsert statement. I've changed that to allow a full reference expression. The fix will be in the next build.
-
repo owner
- changed status to resolved
This was resolved a few builds back. Just forgot to resolve the issue here.
-
Hey Scott,
I'm running v1.8.0.0 and seeing this issue still occurring.
Anyone else seeing this in v1.8.0.0?
-
repo owner
- changed status to open
I'll take a look, Brandon. I thought it had been fixed but sounds like either it was inadvertently regressed or never fully fixed.
-
Thanks Scott!
-
repo owner
- changed version to 1.8.0.4
-
repo owner
Brandon, I'm unable to reproduce this in the version that I'll be releasing tomorrow. Here's a screenshot of the same thing that you've displayed above with no errors:
Please let me know after updating to 1.8.0.4 tomorrow whether this is still an issue for you, and if so, please send me a sample file that reproduces the issue if possible. Thanks!
-
Scott, I'm showing that IC is running 1.8.0.3. I believe I've been auto-prompted to update the plugin before but that's currently not happening. How do I manually update the plugin to the latest version?
Thanks!
-
repo owner
Brandon, I haven't quite released it yet. I'd planned to do so yesterday morning but ended up in a long series of meetings. By the time they were over it was later in the day than I'm comfortable releasing (I prefer to have a good block of hours in case there are any immediate issues). I'm going to post the update in the next hour or two. I'll resolve this issue (and many others) as part of the release process, so that will be your cue to update.
-
Thanks Scott! Very much appreciate your responsiveness on this. Hopefully see you at DF this year?
-
repo owner
Yep, I'll be there. I'm even giving a demo of IC there:
https://success.salesforce.com/Sessions#/session/a2q3A000001ytfTQAQ
Definitely hope to see you there!
-
repo owner
- changed status to resolved
Please reopen if you continue to see this issue in 1.8.0.4.
-
Issue was fixed, thanks Scott!
- Log in to comment
Ah....it's the space-delimited parameter list. Right now my grammar expects a single expression argument. Should be easy enough to address for all of the DML operators by allowing one or more space-delimited expressions to be specified. Thanks for reporting!