Restrictions with the DefaultWebUI

Maybe this is more widely known, however I didn’t know anything about it until recently. We weren’t getting any of our FormFields that were dependent on eachother to work correctly with the DefaultWebUI. After a look into Profiler I saw what was wrong.

Having the DefaultWebUI tag at the end of your spec can look nice, but it’s always better to go ahead and generate your UIModel, because it doesn’t seem to link your FormFields.

It seems that this type of FormFields won’t play together well using the DefaultWebUI.

Therefore you will have to create a UIModel for it and then write your custom code to link everything together.

Posted in CRM

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s