UAD Error Messages in Alamode

[Caterina Platt]

Hello All,

So here's the issue. I have 'Fee' in all fields on the sales grid, yet the error messages are continuing to fire.

Same with the design sometimes.

I've tried several things to clear the fields, then re-enter the data from my Quick Lists just to be sure there are no spaces or other variations. 'delete', Control X, Control K, nothing seems to stop the system from thinking something is different.



I have been simply putting in a '0' on the comparables, cussing a bit at the stupid program, and re-running the E & O to make sure it's clear. It clears the 'issue' and then I sign and ship it on. All good, right?

No. I have a particular client that thinks the '0' needs to go. The items are the same, there shouldn't be a '0'. Yes, Mr. Client, I agree, but what do we do with this idiot program that doesn't? Will you have problems later trying to upload this to the portals when that time comes?

It finally occurs to me that the fields where this is commonly happening are those that auto fill from our entries on the first page. :icon_idea:

Fee Simple auto fills. I prefer Fee. I've been changing it across the board (largely because that's what I already have in my Quick Lists and I'm stubborn that way). Doesn't matter whether the sales grid for the subject is manually filled in to match, cleared via delete, etc. then Quick List.....still the error message.

Apparently the E & O program still 'sees' what auto fills from the first page??? I've got my file shipped to Alamode to see if they can dissect the problem, but wanted to see if others are also experiencing this minor snafu.

 

[Mr Rex]

The fields have to be exactly the same or it comes back with an error if you don't enter 0. Check and make sure the fields don't have an extra space between words or after the last letter. Per Fannie using 0s when there is no difference is not advised, so the client is right in that regard.

 

[Caterina Platt]

The fields have to be exactly the same or it comes back with an error if you don't enter 0. Check and make sure the fields don't have an extra space between words or after the last letter. Per Fannie using 0s when there is no difference is not advised, so the client is right in that regard.

I'm double and triple checking. I'm clearing the fields entirely and starting over with the entry from my Quick Lists just so I know they'll be the same.

It still fires as a damned error and why am I cussing now?

Because the Alamode tech got back to me and 'couldn't understand what the problem was...'

 

[Mr Rex]

try using the quicklist for the subject and F2 for the comparables to see if it still gives the error.

 

[dbiggers]

I'm double and triple checking. I'm clearing the fields entirely and starting over with the entry from my Quick Lists just so I know they'll be the same.

It still fires as a damned error and why am I cussing now?

Because the Alamode tech got back to me and 'couldn't understand what the problem was...'

I'm not sure I understand the problem as you're stating it either. The carry-forwards from the first page aren't even known by the UAD rules -- they have no idea that there's even a relationship between page 1 or 2, they just check the fields to which the rule applies.

Which "errors" exactly are triggering -- and are they in the in-field validation, the review before sending, all of the above? Is the validation saying ALL of the fields are wrong on one row, or just one of them, or more than one and not all? It sounds like there's some sort of spurious data in the field -- some fields, or one field -- making it think there's a difference.

Also, just because E&O thinks it's wrong, you can still send it -- it just says you need to be sure you want to send it even if we think there's a problem. So, if you're confident you're right and we're wrong, ignore the warnings and send it away as you want. You don't have to change the file.

 

[NorthTexValuation]

There is no problem with alamode and UAD. First time I ran E&O I got 6 errors/ warning and two minutes later my template was revised to get onlt the two warnings regarding Prior Sale of Subject fields. No appraiser I've ever heard of abbreviates Fee Simple to Fee, that's just lazy and possibly mileading. Ever heard of Leased Fee? Go through the alamode UAD guide and your problems will be solved.

 

[Caterina Platt]

Hi Dave,

Wow. Between you and Randall Garrett (Apex) talking with us directly through these forums, I have to think we're fairly lucky in this industry.

Let me try to be less convoluted.

Two fields in particular seem to be causing these errors.

Leasehold/Fee Simple

Design (Style)

I'm running into instances where all are identical, not just visually, but I've entered them from the Quick List so I know there are no additional spaces or abbreviation differences. Despite this, the UAD error messages will fire.

I'll see if I can do a screen shot and show you.

I'm Ok with sending it knowing that the error messages aren't accurate as long as I know there isn't some hidden code in there that is going to give the client fits later on when they try to upload into their portals.

 

[Caterina Platt]

There is no problem with alamode and UAD. First time I ran E&O I got 6 errors/ warning and two minutes later my template was revised to get onlt the two warnings regarding Prior Sale of Subject fields. No appraiser I've ever heard of abbreviates Fee Simple to Fee, that's just lazy and possibly mileading. Ever heard of Leased Fee? Go through the alamode UAD guide and your problems will be solved.

:laugh: Lazy and misleading?

Incendiary much?

 

[Caterina Platt]

Hi Dave,

Attached is the screen shot of Comps 1-3. Note the UAD error messages for Fee and Design to Comp 1, yet the entries are the same. Note: I've made certain to clear the fields and start over with Quick List entries just in case there were spaces or something that we couldn't see causing the program to read the entries as dissimilar.

BTW, Stephen Hawkey called back and is working on the issue with me, so I don't want to get several people riled up on the same problem.

Just uploading this for the benefit of those who may be having the same issues.

My client called back after I began this thread, and the reviewer says it is incredibly common right now and he's spending 1/2 his days on the phone regarding the issue.

He also stated without being provoked, '...Alamode is one of the better products. You should see the problems our ACI users are having.'

I don't know if you've heard this much lately, but we appraisers do deeply appreciate all you've done to make this transition as painless as possible and at no extra cost to the appraiser.

Thank you!

 

[Caterina Platt]

Also, just because E&O thinks it's wrong, you can still send it -- it just says you need to be sure you want to send it even if we think there's a problem. So, if you're confident you're right and we're wrong, ignore the warnings and send it away as you want. You don't have to change the file.

Wanted to post an update as Stephen and I just got off the phone.

As to your above quote, Dave: thanks! Part of my concern was that this error code was reading something in the mismo format that our human eyes couldn't discern, and would later cause a problem for our clients as they tried to upload the reports. As I learn from your post, no. It's a 'not to worry' issue. Good!!

What Stephen discovered is that there are some issues in the E & O reader that were conflicting and causing this to happen. He is sending it up to be corrected with the programmers.

In the mean time, we can simply ignore the error messages and move forward as long as we're certain the fields are truly the same.

Hooray!!

Thanks again for all you do, Dave.