Hi Vincent,

You can use the following filtration as an example:

The filtration from the example is added in the Account section. We are using related object filtration (click on the plus button in the first screenshot) to find all accounts where column Number in the object Account communication option contains 000.

I hope this example helps you to build your own filtration. 

Have a great day!

I have a fix for this, not in the Creatio documentation, using ISS Manager edit permissions for the Creatio site, allocate full control to the IIS_IUSRS group.

Hello!

Please grant rights to binary files for the user under which the application pool.

The issue is caused because the user does not have access to the \Terrasoft.WebApp\conf\runtime-data\db.sqlite directory.

In case of any further questions – send them in reply to this message. We would be happy to assist!

Seems to be the same question - https://community.creatio.com/questions/pivot-table-month-comparing-pre…

Hello!

OAuth 2.0 authorization for integrated applications does not  support refresh token flow. The third party application has to generate token and system administrator needs to update the synchronization parameters.

Hello Gabriel,

The custom campaign element was most likely made as an assembly package. In this case, as a fix, the custom element must be created in a regular package.

Otherwise:

1) Check the implementation way according to the article for mistakes

2) "Compile all" application

3) Restart the site with the Redis clearing

If the problem persists after those recommendations, please contact the Creatio technical support team (support@creatio.com) and ask them to check the process for you.

Best regards, 

Anhelina!

Anhelina,

Thank you! I changed to new package with only the campaign files, and changed to simple package and it works! 

Hi,

We have not encountered this problem before.

If the site was deployed locally, we recommend that you additionally check if everything was configured correctly.
You can also contact support with a detailed description at support@creatio.com

You could use this approach in the processes to "expire" the email after a pre-defined period of time.

https://customerfx.com/article/automatically-cancelling-user-tasks-after-a-period-of-time-in-a-creatio-process/

Ryan

Hi Ryan,

Thank you, this was very helpful!

Csilla

Hello,

Please be informed that the Growth license plan has certain limitations, one of which includes restricted access to specific Creatio functionalities, such as the “Setup appearance” settings. To gain access to this feature, you would need to upgrade to at least an Enterprise license type.

For more detailed information regarding the features and limitations of each license type, please reach out to your manager.

Hello,

You should have this section displayed in your Service product. Since the Queues section is only available in Service. However, if you do not see it in Workplace Service, you can add it via the Workplace setup section.

Best regards,
Malika

Hi Malika,

Thanks for your response , I don't see the workplace service in my instance . Could you please tell how to add the Workplace service
Note : Instance is on premise

Best Regards,|
Krishna

Talla bhadra krishna rao,

What is your installation package and site version?

Hi Malika,
 

Name of the Installation package:

8.1.1.3635_SalesEnterprise_Marketing_ServiceEnterprisesoftkey_PostgreSQL_ENU
 

Site Version: 8.1.1.3635
 

Regards,
Krishna

Correct filter for In operator OData 4.01 is usually like:

filter=Id in ('6f2efedd-9b25-43b4-9cb9-0ebe60a02a8a','72509ae9-7065-465c-b7c5-3d193b8fe768')

However, it produces the same result with Creatio OData. It's possible Creatio only implements OData 4.0 and not 4.01 (which introduced the In operator).
Might need a different approach like a configuration service that takes the like of values as a param and returns the results? Or if it would work to create a common parent record of the values that could be used to retrieve the results?

Ryan Farley writes:

Correct filter for In operator OData 4.01 is usually like:

filter=Id in ('6f2efedd-9b25-43b4-9cb9-0ebe60a02a8a','72509ae9-7065-465c-b7c5-3d193b8fe768')

However, it produces the same result with Creatio OData. It's possible Creatio only implements OData 4.0 and not 4.01 (which introduced the In operator).
Might need a different approach like a configuration service that takes the like of values as a param and returns the results? Or if it would work to create a common parent record of the values that could be used to retrieve the results?

Hi Ryan,

I did try that syntax already, but it didn't work.

Maybe someone from Creatio can shed some light on the implemented OData version?

Thanks,

Robert

Hello,

The 'in' operator is not supported in OData 4 in Creatio.
At the moment, it is possible to use the operators that are available in the examples in the official Postman collection of the Creatio API.
We have registered a task to improve this functionality ('in' operator for Creatio OData 4 requests) in future releases of Creatio.
 

Serhii Parfentiev,

Thanks for the information!

Since the documentation I linked explicitly points to the OData 4.01 version, it should be updated and the exact version should be mentioned to know what is supported and what is not.

Thanks,

Robert