Apex Code Development You need to sign in to do that
Don't have an account?
Will someone revise the "Define Custom Big Objects" Trailhead unit?
This unit is being pushed as intermediate even though it is missing critical steps towards making use of the material it is presenting, such as step-by-step information how to successfully push the metadata we create and make use of the permissions we are uploading.
As far as I can tell, I am successfully uploading the Customer_interaction_Big_Object.permissionSet through ForceIDE, as I get no errors after save to server, but then this permission set isn't available for me to assign to anyone when I look in the SFDC setup UI for permission sets.
And then I can't upload the data because the object isn't writable, presumably because I don't have permissions.
Morever, the sample "Apex" script isn't even valid Apex. For examples:
* There shouldn't be any angle brackets in: <Customer_Interaction__b> bo = new Customer_Interaction__b();
* Strings should use single quotes, not double quotes: bo.Account__c = "001R000000302D3";
* Play_Duration__c was defined as a number, not text (and again, double quotes!): bo.Play_Duration__c = "25";
Doesn't anyone give these articles a test drive before publishing them to people who will rely on them?
As far as I can tell, I am successfully uploading the Customer_interaction_Big_Object.permissionSet through ForceIDE, as I get no errors after save to server, but then this permission set isn't available for me to assign to anyone when I look in the SFDC setup UI for permission sets.
And then I can't upload the data because the object isn't writable, presumably because I don't have permissions.
Morever, the sample "Apex" script isn't even valid Apex. For examples:
* There shouldn't be any angle brackets in: <Customer_Interaction__b> bo = new Customer_Interaction__b();
* Strings should use single quotes, not double quotes: bo.Account__c = "001R000000302D3";
* Play_Duration__c was defined as a number, not text (and again, double quotes!): bo.Play_Duration__c = "25";
Doesn't anyone give these articles a test drive before publishing them to people who will rely on them?
As i promised:
The way i founded to successfuly deploy the big object was using ant (force.com migration tool), if you don't know how to use ant please refer to this_article (https://developer.salesforce.com/docs/atlas.en-us.daas.meta/daas/forcemigrationtool.htm) or let me know. Check picture to see the folder structure:
Like any traditional ant package, i added the Rider_History__b.object inside a 'objects' folder and Ride_History_Big_Object.permissionSet inside a 'permissionsets' folder. I used the same package.xml provided in the trailhead excersise and i used the following ant scripts:
1- build.xml
<project name="Deploy Big Object" default="deployBig" basedir="." xmlns:sf="antlib:com.salesforce"> <property file="build.properties"/> <property environment="env"/> <target name="deployBig"> <sf:deploy username="${sf_target.username}" password="${sf_target.password}" serverurl="${sf_target.serverurl}" deployRoot="${sf.code_folder}" checkOnly="false" runAllTests="false" logType="Debugonly" pollWaitMillis="99999" maxPoll="999"/> </target> </project>2 - build.properties
3 - package.xml
<?xml version="1.0" encoding="UTF-8"?> <Package xmlns="http://soap.sforce.com/2006/04/metadata"> <types> <members>*</members> <name>CustomObject</name> </types> <types> <members>*</members> <name>PermissionSet</name> </types> <version>41.0</version> </Package>Hope this colud help you guys!
There are two possible reasons:
- Check the deployment result on Deployment Status in Setup, see if you really deployed any component (on my first successfull big-object deploy i saw that i wasn't sending any component with my deploy, that's why i used the force.com migration tool over workbench)
- Check if you deployed the permissions for the big object, otherwise you won't have view access
Thanks for adding these details, though really they belong in the Trailhead article instead of this information silo.
That said,
1. I'm familiar with ANT; I just used ForceIDE because it was already set up and I was lazy about creating the build script.
2. Is there any reason we shouldn't use ForceIDE to upload this metadata? So far as I know, both custom permssion and object metadata are supported through ForceIDE.
3. Even using ANT, I'm getting a silent failure.
More specifically, the new permission set still doesn't display in SFDC UI even though this is the feedback from the migration tool:
C:\training\sfdc\Trailhead12\etc\BigObject>ant deployBig
Buildfile: C:\training\sfdc\Trailhead12\etc\BigObject\build.xml
deployBig:
[sf:deploy] Request for a deploy submitted successfully.
[sf:deploy] Request ID for the current deploy task: 0Af0Y00001E541RSAR
[sf:deploy] Waiting for server to finish processing the request...
[sf:deploy] Request Status: InProgress
[sf:deploy] Request Status: Succeeded
[sf:deploy] *********** DEPLOYMENT SUCCEEDED ***********
[sf:deploy] Finished request 0Af0Y00001E541RSAR successfully.
BUILD SUCCESSFUL
Total time: 1 minute 43 seconds
And these are the Deployment details in Deployment status:
Deployment Succeeded
Name: 0Af0Y00001E541R
Type: API
Deployed By: Brian Kessler
Start Time: 24/10/2017 14:11
End Time: 24/10/2017 14:11
Thanks,
-Brian.
Sorry about the issues. If you're having issues with deployment, can you try redeploying with the "permissionSet" file extension in all lowercase ("permissionset")? We've revised the module (changes are now live) to no longer refer to permissionset as "permissionSet", and all references to the file are now in lowercase. I know that if you deploy a "permissionSet" file through Workbench, the permissions don't get included in the deployment.
I'll look into the Apex example for you as well.
Thanks in advance
Manoj Tiwari