Custom Field Updates

[josh-pratt]

The field ID support in this solution is really great and seems to work well. However, there seems to be a problem when trying to save updates back to the loan when those updates are to custom fields. For example, the following flawlessly updates the loan number field in the loan and successfully records that update back to Encompass.

loan.Fields["364"].Value = "987654321";
await client.Loans.UpdateLoanAsync(loan);

Further, the following successfully updates the custom fields for the loan in memory.

loan.Fields["CX.STRINGFIELD"].Value = "Value1";
loan.Fields["CX.DATEFIELD"].Value = DateTime.Today.Date;
loan.Fields["CX.NUMERICFIELD"].Value = 255;

But, then subsequently, when trying to write those changes back to Encompass, the changes are not successfully recorded in the Encompass loan file.

await client.Loans.UpdateLoanAsync(loan);

I seem to remember a while back running into a similar problem when trying to update custom fields using Ellie Mae's API directly without EncompassRest, but it has been so long, that I don't recall exactly what happened.

Guidance?

[josh-pratt]

@TylerBrinkley, am I the only one seeing this issue?

[rbpeterson2]

I’m curious as to if you tried to update those same values just using Postman … we haven’t run into any update issues to custom fields as of yet unless they are tied to field data entry rules. From: Josh Pratt ***@***.***> Sent: Friday, August 13, 2021 11:44 AM To: EncompassRest/EncompassRest ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [EncompassRest/EncompassRest] Custom Field Updates (#396) CAUTION: This email originated from outside your organization. Exercise caution when opening attachments or clicking links, especially from unknown senders. @TylerBrinkley<https://github.com/TylerBrinkley>, am I the only one seeing this issue? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#396 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGJV2UYMRMYNYHZULERXUDTT4U4SFANCNFSM5B24HPNA>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>. TVMA, Inc. trades as Teraverde Management Advisors | Intellectual Property provided by Teraverde Financial Confidential Electronic Mail Notice: The information contained in this message is intended only for the persons to whom it is addressed and may contain privileged material. Copying, distributing, dissemination, reliance on, or other use of the information by persons other than the intended recipient(s) is prohibited. If you received this message in error, please notify the sender and delete the entire message from any computer.

[AndrewAguayo]

What I had to do was create a separate loan object, set only the custom fields that were needed, then perform an update.

Loan loan = new Loan(client,loanId);
loan.Fields["whatever custom field"].Value = "whatever value";
await client.Loans.UpdateLoanAsync(loan);

This kept the json only to the customfield entity and worked for the last 2 years.

However since July of this year, I'm having problems updating new created custom fields that added to a previously existing loan.

I have tested this in Postman using EllieMae's provided collection. The V1 endpoint returns 204 No Content, but the field is not updated. V3 completely fails with a 400 Bad Request.

{
"summary": "Bad Request",
"details": "Request Payload has errors",
"errors": [
{
"summary": "documentContracts.customFields",
"details": "Invalid field name or value"
}
]
}

Still have pending cases with EllieMae on this.

[TimH-SL]

Could my latest issue be related?

#401