function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Jason Kuzmak 12Jason Kuzmak 12 

Cannot deploy big object through Workbench. A pseudo attribute name is expected.

While trying to complete the challenge deployment of a big object through trailhead, workbench repeatedly tells me:

User-added image

I know what you're going to say. "Jason, just throw a question mark onto the end of the attribute name. That's documented everywhere."
And you're right. Every source I see on Google tells me to simply encapsulate everything with included question marks on both sides. 

But lo, it's already there. Here's my object file:
 

<?xml version="1.0" encoding="UTF-8"?>
<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
<deploymentStatus>Deployed</deploymentStatus>
    <fields>
        <fullName>Start_Location_Lat__c</fullName>
        <label>Start Location Latitude</label>       
        <required>false</required>
        <type>Number</type>      
        <scale>4</scale>
        <precision>7</precision>
    </fields>
    <fields>
        <fullName>Start_Location_Long__c</fullName>
        <label>Start Location Longitude</label>       
        <required>false</required>
        <type>Number</type>   
        <scale>4</scale>
        <precision>7</precision>
    </fields>
    <fields>
        <fullName>Start_Time__c</fullName>
        <label>Start Time</label>
        <required>true</required>
        <type>DateTime</type>
        <unique>false</unique>
    </fields>
    <fields>
        <fullName>End_Time__c</fullName>
        <label>End Time</label>
        <required>false</required>
        <type>DateTime</type>
        <unique>false</unique>
    </fields>
    <fields>
        <fullName>Service_Type__c</fullName>
        <label>Service Type</label>
        <length>16</length>
        <required>false</required>
        <type>Text</type>
        <unique>false</unique>
    </fields>
    <fields>
        <fullName>Rider_Account__c</fullName>
        <label>Rider Account</label>
        <length>16</length>
        <required>true</required>
        <type>Text</type>       
    </fields>
    <fields>
        <fullName>Rider_Rating__c</fullName>
        <label>Rider Rating</label>       
        <required>false</required>
        <type>Number</type>
        <unique>false</unique>
        <scale>1</scale>
        <precision>2</precision>
    </fields>
    <indexes>
        <fullName>Rider_History_Index</fullName>
        <label>Rider History Index</label>
        <fields>
            <name>Rider_Account__c</name>
            <sortDirection>DESC</sortDirection>
        </fields>
        <fields>
            <name>Start_Time__c</name>
            <sortDirection>DESC</sortDirection>
        </fields>       
    </indexes>
    <label>Rider History</label>
    <pluralLabel>Rider Histories</pluralLabel>
</CustomObject>
I'm not sure what it doesn't like about the pseudo attribute name, anyone see anything wrong?
Best Answer chosen by Jason Kuzmak 12
Jason Kuzmak 12Jason Kuzmak 12

Update: I was able to create my own big object and deploy successfully by strictly using the xml editor in Eclipse. The problem above was caused (as far as I can tell) by a malformed xml document that I was manipulating through the Eclipse "source" tab, Notebook, and various programs that no doubt were putting their own spin on things, using copy/pasted code from other forum threads :D

So, everything was encapsulated correctly, but observing the document in the design tab showed a bunch of blank lines with string icons next to them.
User-added image

Anyway, all fixed, but thank you for your help!

All Answers

Raj VakatiRaj Vakati
Try this 
 
<?xml version="1.0" encoding="UTF-8"?>  
<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">  
   <deploymentStatus>Deployed</deploymentStatus>  
   <fields>  
     <fullName>Start_Location_Lat__c</fullName>  
     <label>Start Location Latitude</label>  
     <required>false</required>  
     <type>Number</type>  
     <unique>false</unique>  
     <scale>4</scale>  
     <precision>7</precision>  
   </fields>  
   <fields>  
     <fullName>Start_Location_Long__c</fullName>  
     <label>Start Location Longitude</label>  
     <required>false</required>  
     <type>Number</type>  
     <unique>false</unique>  
     <scale>4</scale>  
     <precision>7</precision>  
   </fields>  
   <fields>  
     <fullName>Start_Time__c</fullName>  
     <label>Start Time</label>  
     <required>True</required>  
     <type>DateTime</type>  
     <unique>false</unique>  
   </fields>  
   <fields>  
     <fullName>End_Time__c</fullName>  
     <label>End Time</label>  
     <required>false</required>  
     <type>DateTime</type>  
     <unique>false</unique>  
   </fields>  
   <fields>  
     <fullName>Service_Type__c</fullName>  
     <label>Service Type</label>  
     <length>16</length>  
     <required>false</required>  
     <type>Text</type>  
     <unique>false</unique>  
   </fields>  
   <fields>  
     <fullName>Rider_Account__c</fullName>  
     <label>Rider Account</label>  
     <length>16</length>  
     <required>true</required>  
     <type>Text</type>  
     <unique>false</unique>  
   </fields>  
   <fields>  
     <fullName>Rider_Rating__c</fullName>  
     <label>Rider Rating</label>  
     <required>false</required>  
     <type>Number</type>  
     <unique>false</unique>  
     <scale>1</scale>  
     <precision>2</precision>  
   </fields>  
   <indexes>  
     <fullName>Rider_History_Index</fullName>  
     <label>Rider History Index</label>  
     <fields>  
       <name>Rider_Account__c</name>  
       <sortDirection>DESC</sortDirection>  
     </fields>  
     <fields>  
       <name>Start_Time__c</name>  
       <sortDirection>ASC</sortDirection>  
     </fields>  
   </indexes>  
   <label>Rider History</label>  
   <pluralLabel>Rider History</pluralLabel>  
</CustomObject>

 
Jason Kuzmak 12Jason Kuzmak 12

Hi Raj,

End_Time__c already had a unique setting of 'false', but I added it to Start_Location_Lat__c. No change.

I ended up finding a pre-made zip of the correct documents that someone uploaded in the forum. I double-checked it with the file I created. The lines are almost identical, and the only differences were the spacings. There were some other carriage returns in the downloaded file that I didn't have, and that package deployed perfectly. 

Also, I created my object file in Eclipse. I'm not sure if that has something to do with it. 

 

Jason Kuzmak 12Jason Kuzmak 12

Update: I was able to create my own big object and deploy successfully by strictly using the xml editor in Eclipse. The problem above was caused (as far as I can tell) by a malformed xml document that I was manipulating through the Eclipse "source" tab, Notebook, and various programs that no doubt were putting their own spin on things, using copy/pasted code from other forum threads :D

So, everything was encapsulated correctly, but observing the document in the design tab showed a bunch of blank lines with string icons next to them.
User-added image

Anyway, all fixed, but thank you for your help!

This was selected as the best answer