-
Notifications
You must be signed in to change notification settings - Fork 396
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BulkForceClient on nuget #246
Comments
(Also couldn't find it with a search in the repo, so not sure what code the readme is referring to...?) |
It's at the moment only a beta version: https://www.nuget.org/packages/DeveloperForce.Force/1.4.0-beta |
I'm in the process of writing my own BulkForceClient as well. Seems to be unimplemented in ForceToolkitForNet at this time as their JobInfo class only contains a fraction of what the actual documentation specifies: https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/asynch_api_reference_jobinfo.htm I'm essentially creating a class derived from ForceClient as a base class, "hiding" methods in base that I'm re-implementing using the Example:
Will keep you posted on how it goes :) |
For now at least...I'm able to create batch upsert jobs, specifying which field will be my The primary "enabler" for being able to create this was to expose PR submitted: #248 |
Are we sure BulkConstants is in 1.4.0-beta? I've got that installed in my project but can't find/use BulkConstants, CreateJobAsync etc. However if I clone the latest master branch from github and reference it that way in my project i DO see it. Unfortunately for some reason when I reference the full code/branch this way my web app hangs on any Salesforce connection then so I can't use this method for now. Which is why I'm trying to find out how/if we can get BulkConstants via nuget right now or not. |
If this is still an issue (see latest updates to code) please re-open with more specifics. |
We've got the latest version of the nuget package installed (1.3.2) but can't find the
BulkForceClient
in there. Is the nuget package out of date?The text was updated successfully, but these errors were encountered: