I still have to wrap it in a CL to get the PROFOUNDUI library, so I will be looking for that fix. For the time being I can move forward and look into your other suggestions. We can close this thread out as being resolved as far as I am concerned. Thanks for your timely and on-point responses.
FYI - follow up: In the last post on this issue I stated that we have a workaround wrapping the call with a CL to provide the PROFOUNDUI (or custom install) library. This is a workaround for us and it appears that we may have to revisit the temporary solution in the not too distant future. The Profound fix is still high on our priority and management is asking that I follow up asking when we might see it. I will be looking for the fix so that we can drop the temporary CL wrapper solution. There is some differing opinion on client installs. I will start another thread if we need to get into details there.
The base issue and reason for the thread has been answered. The conversion to use Profound is looking beautiful. Thanks again Scott and team.