Bug fix - Permit Priority value is not required

Issue 86
apex-enterprise-patterns · Aug 15, 2023 · f1c35a3 · f1c35a3
1 parent 1e963d0
commit f1c35a3
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/.../schema/objects/ApplicationFactory_SelectorBinding__mdt/fields/Priority__c.field-meta.xml b/.../schema/objects/ApplicationFactory_SelectorBinding__mdt/fields/Priority__c.field-meta.xml
@@ -7,7 +7,7 @@
     <inlineHelpText>When multiple concrete classes are specified for a SObject, the number specifies which concretion should be returned.  Higher numbers are higher priority; null values are the least priority.</inlineHelpText>
     <label>Priority</label>
     <precision>4</precision>
-    <required>true</required>
+    <required>false</required>
     <scale>0</scale>
     <type>Number</type>
     <unique>false</unique>

diff --git a/...n/schema/objects/ApplicationFactory_ServiceBinding__mdt/fields/Priority__c.field-meta.xml b/...n/schema/objects/ApplicationFactory_ServiceBinding__mdt/fields/Priority__c.field-meta.xml
@@ -7,7 +7,7 @@
     <inlineHelpText>When multiple concrete classes are specified for an interface, the number specifies which concretion should be returned.  Higher numbers are higher priority; null values are the least priority.</inlineHelpText>
     <label>Priority</label>
     <precision>4</precision>
-    <required>true</required>
+    <required>false</required>
     <scale>0</scale>
     <type>Number</type>
     <unique>false</unique>