Anybody releasing a suiteapp to both one world an...
# sdf
m
Anybody releasing a suiteapp to both one world and non oneworld accounts? The record seems to deploy with a subsidiary field without issues but it fails on the form everytime
d
PRO-TIP: Never reference OneWorld-only record types. Use id's instead
m
what do you mean? How would you deploy a subsidiary type select field? I think the form is having an issue because when the record gets deployed, it gets rid of the field but it's still on the form and then throws an error
This is the field in the custom record
Copy code
<customrecordcustomfield scriptid="custrecord_nact_task_subsidiary">
  <accesslevel>2</accesslevel>
  <allowquickadd>F</allowquickadd>
  <applyformatting>F</applyformatting>
  <checkspelling>F</checkspelling>
  <defaultchecked>F</defaultchecked>
  <defaultselection></defaultselection>
  <defaultvalue></defaultvalue>
  <description></description>
  <displayheight></displayheight>
  <displaytype>NORMAL</displaytype>
  <displaywidth></displaywidth>
  <dynamicdefault></dynamicdefault>
  <encryptatrest>F</encryptatrest>
  <fieldtype>SELECT</fieldtype>
  <globalsearch>F</globalsearch>
  <help></help>
  <isformula>F</isformula>
  <ismandatory>F</ismandatory>
  <isparent>F</isparent>
  <label>Subsidiary</label>
  <linktext></linktext>
  <maxlength></maxlength>
  <maxvalue></maxvalue>
  <minvalue></minvalue>
  <onparentdelete>NO_ACTION</onparentdelete>
  <parentsubtab></parentsubtab>
  <rolerestrict>F</rolerestrict>
  <searchcomparefield></searchcomparefield>
  <searchdefault></searchdefault>
  <searchlevel>2</searchlevel>
  <selectrecordtype>-117</selectrecordtype>
  <showinlist>F</showinlist>
  <sourcefilterby></sourcefilterby>
  <sourcefrom></sourcefrom>
  <sourcelist></sourcelist>
  <storevalue>T</storevalue>
  <subtab></subtab>
</customrecordcustomfield>
Then in the form
Copy code
<field>
  <id>[scriptid=customrecord_nact_task.custrecord_nact_task_subsidiary]</id>
  <label>Subsidiary</label>
  <visible>T</visible>
  <mandatory>F</mandatory>
  <displayType>NORMAL</displayType>
  <columnBreak>F</columnBreak>
  <sameRowAsPrevious>F</sameRowAsPrevious>
  <quickAdd>F</quickAdd>
</field>
n
Custom subsidiary fields work fine in non-Oneworld accounts when deployed via non-SDF SuiteApps. Accounts where OneWorld is not enabled show a single value "Parent Company" (Internal Id: 1) in the custom subsidiary select field.
m
Have you deployed forms with the subsidiary field? that's what is throwing an error for me
n
Yes. We have custom records with custom subsidiary fields on custom forms which are deployed as non-SDF SuiteApps via managed bundles. It works perfectly. So I suspect this is an SDF validation issue only.
m
Yes. We have the same but this is our first true suiteapp and it looks like it's most likely a defect