You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix#1 — replace GetObjectLookup with GetLookupField: fix misleading parameter order (objectKey before lookupKey caused ArgumentException when called with two arguments)
Copy file name to clipboardExpand all lines: Client.Scripting/PayrollEngine.Client.Scripting.xml
+6-5Lines changed: 6 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -6352,7 +6352,7 @@
6352
6352
<returns>The typed lookup value, or <c>default(T)</c> when the key is not found</returns>
6353
6353
<remarks>
6354
6354
When the stored value is a JSON object and <typeparamref name="T"/> is not <c>string</c>,
6355
-
the JSON is deserialized automatically. Use <see cref="M:PayrollEngine.Client.Scripting.Function.PayrollFunction.GetObjectLookup``1(System.String,System.String,System.String,System.String)"/>
6355
+
the JSON is deserialized automatically. Use <see cref="M:PayrollEngine.Client.Scripting.Function.PayrollFunction.GetLookupField``1(System.String,System.String,System.String,System.String)"/>
6356
6356
to extract a single property from a JSON-object lookup value.
6357
6357
</remarks>
6358
6358
</member>
@@ -6362,12 +6362,13 @@
6362
6362
<param name="lookupKeyValues">The lookup key values (serialized to JSON string)</param>
6363
6363
<param name="culture">The culture, null for the system culture (optional)</param>
0 commit comments