Mendix 7 is no longer supported unless you have Extended Support (for details, please contact Mendix Support). Mendix 7 documentation will remain available for customers with Extended Support until July, 2024.
Special checks
Checking for an Empty Object
Input
An object.
Type: Any type of object.
Output
Returns whether the object is empty.
Type: Boolean.
|
|
Assuming $object1 is a domain entity and that currently exists, this statement will return False. Conversely, if the object does not currently exist (which is possible if you try to retrieve a non-existent object), it will return True.
The same holds for when $object1 is a variable (such as Integer, String etc).
Checking for an Empty Object Member
Input
A member (attribute or association) of an object.
Type: Any type of member.
Output
Whether the attribute is empty.
Type: Boolean.
|
|
Assuming $object1 is an domain entity and that it has a member called ‘member1’, the following table illustrates what this statement will return:
| member1 has a value | member1 does not have a value | |
|---|---|---|
| $object1 has a value | false | true |
| $object1 has no value | N/A | true |
Checking Whether an Object Is New
Input
An object.
Type: Any type of object.
Output
Returns whether the object is new (created but not yet committed). Note this only holds when this function is called on the variable which represents the created object. When the object is retrieved from the database isNew will always yield false.
Type: Boolean.
|
|
Checking Whether an Object Is Synced
This function is available only in expressions for conditional visibility or editability, as only they are evaluated client-side.
This was added in Mendix 7.1.
Input
An object.
Type: Any type of object.
Output
Returns whether the changes done to the object offline have been synchronized to the runtime database. In web profiles and hybrid profiles without offline support, this always returns true.
Type: Boolean.
|
|