Tyler Brinkley

While not ideal, aren't those exceptions being swallowed here? https://github.com/EncompassRest/EncompassRest/blob/v1.2.x/src/EncompassRest/Loans/LoanFieldDescriptors.cs#L606

Is the request message not sufficient for this? Any ideas of how to achieve this?

It sounds like a Field Data Entry rule that requires fields [1069], [981], and [122] to be entered before populating [CX.DISCLOSURE].

I believe only super admin accounts can do that within the smart client. I'm not sure if it's the same for the API's.

It doesn't work like that. I think you need to fix the Field Data Entry rule.

There are differences in how business rules are executed from the API vs SDK, intentional or otherwise by ICE (Ellie Mae). You can apply a borrower pair index to a...

I believe this issue only occurs for users where document conversion is used. I suggest you contact Ellie Mae, they should be able to steer you in the right direction,...

I'd suggest you use the newly supported Export Attachments API. See the unit test here for an example. https://github.com/EncompassRest/EncompassRest/blob/b7d0492dd788544145a3a6691dc27a100113f3cb/src/EncompassRest.Tests/LoanAttachmentTests.cs#L106-L112

I was able to reproduce this issue in a unit test. I've examined the json that's returned by the Encompass API and it doesn't appear the value is being returned...

That's really strange. It was failing for me yesterday. I think they must have fixed something.