10,730
edits
Important: Deprecating old WebView — Publish failed error
Rules editor: Difference between revisions
Jump to navigation
Jump to search
→Using variables
| Line 639: | Line 639: | ||
If you stumble into an "Entity Not Loaded" error when executing rules, use the ContainsData operator to check if a variable has been populated before proceeding with your rule's logic. | If you stumble into an "Entity Not Loaded" error when executing rules, use the ContainsData operator to check if a variable has been populated before proceeding with your rule's logic. | ||
=== Deleting variables === | === Deleting variables === | ||
| Line 687: | Line 678: | ||
* LoadReference: Load a related record from related entity. | * LoadReference: Load a related record from related entity. | ||
* LoadFetch: Load a particular record from the database. Opens a new [[Filter editor]] window that allows you define a [[FetchXML]] command that finds the record. | * LoadFetch: Load a particular record from the database. Opens a new [[Filter editor]] window that allows you define a [[FetchXML]] command that finds the record. | ||
=== Shared entity limits === | |||
There's a limit to how many shared variables you can use. | |||
* On forms and questionnaires, you can use up to 1000 shared variables. | |||
* On views, you can use up to 750 shared variables. | |||
The app displays an error if you go past this limit. | |||
{{Note|This usually happens when you use shared variables of the type "entity". In fact, this adds a shared variable '''for each field''' of the entity. If you add a huge entity with many fields, you can run into the limit.}} | |||
=== Global constants === | === Global constants === | ||