FAQ

Sometimes, it can be difficult to understand how interpreted temporal values behave. Therefore, we've prepared a simple tutorial to help you figure it out.

1) Go to https://onlinephp.io/. You will see something like this:

2) Replace all the text with the following, replacing <enter temporal value here> with whatever you need to try out. Be sure to keep the double quotes "!

Here's an example:

3) Press "Execute code" and you will see the result of your interpreted temporal value appear bellow:

This is usually caused by a trailing space at the end of the query. Press the right arrow [→] repeatedly to get to the end of the query, and remove any trailing spaces. If this doesn't help, delete the entire query and type it from scratch.

This is a technical problem that can usually be solved by setting up appropriate database indexes. Please contact your SugarCRM partner or representative and describe the issue to them, including the exact query you used. They will know what to do.

When you use both, the conditions are connected with and. For example, the following searches for Accounts whose name starts with "Abc", and whose Billing Country is "USA":

The ID of a record, which can then be used when querying by ID, can always be found in the address bar when you are viewing the record. However, it depends on whether the module is "new style" or "old style".

For reference, this is what an "old-style" module looks like:

The address in the address bar always starts with #bwc:

In modules like these, when you open up a specific record, the ID will be located right after record=, as seen in the picture below.

For reference, this is what a "new-style" module looks like:

The address bar does not start with #bwc, but rather #<module name>, e.g. #Accounts.

In modules like these, when you open up a specific record, the ID will be located right after the #<module name> part, as seen in the picture below.

While exceedingly unlikely, a situation may arise where some specific query causes an error to occur inside Sugar. When that happens, Sugar displays an error page similar to the following:

Since, like regular filters, the last query is saved and executed whenever a module is open, this will cause the module to be unopenable, as opening the module will immediatelly trigger the query and cause the error.

If such a situation occures, use the Clear and refresh button located in your profile-actions menu:

This will cause QuickQuery to temporarily forget the last query entered in all modules. Be aware that this only lasts until you refresh the page, unless you overwrite the old query with a new query. Therefore, after using this button, apply any kind of valid query (in QuickQuery) to the module the error occurred in. This will overwrite the query which was causing the error. After that, refresh the page, which will restore the last queries in other modules.