You need to sign in to do that
Don't have an account?
Riad Gulabkhan 10
Cannot validate big object module
Hi,
I'm trying to validate the big object module where I have to create the big object : Rider history.
After creating the 3 xml files, zip them and deploy them using the workbench (without any error), When I go back to Salesforce to make sure that the big object is created, no big object is available.
Does I miss something ?
I thought that my xml files were not good so I tried to create another really simple big object. It wasn't successfull
Can someone provide an example of xml files (not what is available on the internet because I tried them but some that lead to really create big object into salesforce)
Thanks a lot
I'm trying to validate the big object module where I have to create the big object : Rider history.
After creating the 3 xml files, zip them and deploy them using the workbench (without any error), When I go back to Salesforce to make sure that the big object is created, no big object is available.
Does I miss something ?
I thought that my xml files were not good so I tried to create another really simple big object. It wasn't successfull
Can someone provide an example of xml files (not what is available on the internet because I tried them but some that lead to really create big object into salesforce)
Thanks a lot
Verify:
- <length>7</length> (text) and <precision>7</precision> (number)
- All the full Names ( Start_Location_Latitude__c or Start_Location_Lat__c ?)
- The orders ASC and DESC
- For the numbers, date times:
Use this order:<unique>false</unique>is useless.<fields>
<fullName>Start_Location_Lati
tude__c</fullName><label>Start Location Latitude</label>
<required>false</required>
<type>Number</type>
<scale>4</scale>
<precision>7</precision>
<unique>false</unique>// useless for numbers and datetimes</fields>
Fields:
Start_Location_Lat__c
Label: Start Location Latitude
Required: False
Type: Number
Unique: False
Precision: 7
Scale: 4
All Answers
The deploymeny is not explained. The easiest way is to use the workbench (zero local installation needed).
If you are using only your playground currently (you must be connected), the connection with the workbench will be direct from the following URL:
https://workbench.developerforce.com/login.php
1) select "Single Package" (and "Check Only" for verification without deploying)
2) package.zip with three files and two folders (/objects/ and /permissionsets/ ) :
- objects/Rider_History__b.object
- permissionsets/Rider_History_Big_Object.permissionset
- package.xml
package.xmlI need to add a label (missing in the trailhead challenge) for the permission set.
By the way, I need to pass all the superbadges (done) and all the technical trailhead challenges (progressively) if I want to help the people here about any of them.
Regards
The workbench is the Swiss knife of all the developers and administrators of Salesforce.
I identified what was not good : the folder tree was not correct
After changing that, i'm still not able to create a big object. No big object is displayed on Salesforce
I don't understand.
I will try with another trailhead org
The robot only tests the result of this file (the permission set is useless).
Here the Rider_History__b.object file
Thanks
Verify:
- <length>7</length> (text) and <precision>7</precision> (number)
- All the full Names ( Start_Location_Latitude__c or Start_Location_Lat__c ?)
- The orders ASC and DESC
- For the numbers, date times:
Use this order:<unique>false</unique>is useless.<fields>
<fullName>Start_Location_Lati
tude__c</fullName><label>Start Location Latitude</label>
<required>false</required>
<type>Number</type>
<scale>4</scale>
<precision>7</precision>
<unique>false</unique>// useless for numbers and datetimes</fields>
Fields:
Start_Location_Lat__c
Label: Start Location Latitude
Required: False
Type: Number
Unique: False
Precision: 7
Scale: 4
Sorry for the late reply, I was really busy at work
Thanks a lot, I finally manage to create a big object and validate the trailhead level
Regards
Riad
I have just passed this module but for sure in 25 minutes.
My issue was the filenames for the object and the permissions.
Exactly the fileextensions were not correct
package.xml
objects/<myBigObject>.object // no .xml euxtension
permissionSets/<myPermission>.permissionset // no .xml extension
Under windows, uncheck option to hide extensions on known file type to verify the file extensions
Regards
Eric