So this is what I stumbled on with SCA and having the aero.sors update as well. I managed to fix the issue for the SCA field, but had to do some ADE and XML work to do so. I made those available to the community.
That said, I am going to be in the camp with a base dataset having the field as KBVU. I don't plan on updating to v5 right away regardless of if it has 61B or BVU in the default dataset, so I'd like to get a fix regardless. I imagine, if I have to do it myself, it will be the same ADE and XML work required for at least one of the BGL's for this product. I am however, hoping a fix is coming for those of us who do have updated data, but aren't eager to make the migration to v5. This was to be a day one purchase for me, but I know (as I had a feeling) that it was going to have a conflict. Again, I am not going to have any meaningful time to sit down with it though for a day or two. @kmelz I understand your rule out technique. I am in the same camp you are. The fix is to either find a default, unmodified APX17190 as you are searching for, leave it disabled (not ideal), or have the Boulder City bgl's corrected to reflect BVU instead of 61B. If I make headway on it before it gets addressed here, I'll post a follow up. Keep this thread bookmarked though, because this is going to be a popular support topic :-)