Clear Warning Messages

5 minutes to read Download PDF Edit

1 Introduction

This how-to explains how to eliminate design time warnings. While these warnings will not cause the application to break, it is important to fix them to keep a clean project.

After using this how-to, you will know how to do the following:

  • View warning messages
  • Clear warning messages

2 Viewing Warning Messages

Warning messages can be seen in the Error List tab of the Modeler (by default shown at the bottom of the Modeler). Note that the Warnings box must be selected for them to display.

If this tab is not visible, it can be displayed via the View menu by selecting the Error List option:

To get more information, double-click or right-click the warning.

3 Common Warnings

  • This will not affect the project in this version of the Modeler, but it may cause problems when upgrading
  • In this example, the pop-up layout must be adjusted in order to no longer use the main placeholder
  • Once the microflow has split due to an error, the flow that executes due to the error should not merge with the flow that executes when no error occurs
  • The security for the System.FileDocument entity has a default setting that which can cause security loopholes
  • This warning suggests creating specialized entities to eliminate such scenarios
  • Data source microflows should not have an effect on the client
  • This microflow likely has a show message or show page activity that should be removed
  • The specified caption or title is empty
  • This should be populated so that the page will be understood
  • This should be populated to ensure the page will be understood (similar to the “empty caption” above)
  • The selected progress message is empty, but it should be populated
  • This context is read-only, but there are events set on the field (either on-change, on-leave, or on-enter)
  • There is no need for a microflow that is not accessed through navigation, a page, or a published app service to have security roles allowed
  • This can lead to a security problem, and the assigned roles should be removed
  • This microflow performs no functionality; it should be removed or functionality should be added
  • The module role cannot be used by any users
  • This module role should either be removed or assigned to a user role so that the proper security is enforced
  • When using a form for a reference selector, the constraint should be set on the reference selector (not on the form)
  • On a page, a field can be set to required
  • When the field is set to required, the Required Message should be set
  • In this case, either the Required Message must be set or the field must not be required
  • This is similar to the previous warning
  • If the field is not required, the Required Message should be empty
  • If the Required Message was set with the intention of making the field required, the field should be made required
  • Edit the published web service to include a proper namespace
  • There are multiple potential causes here
  • The solution involves removing the variable from the microflow, which could mean deleting the retrieve activity or electing to not use the return value of a microflow call

Several warnings relate to improper security. For more information on this, see the Project Security chapter of the Mendix Reference Guide.

Copyright © Mendix. All rights reserved. | Mendix.com | Terms of Use | Privacy Policy