Hello,

Please note that we do not recommend deleting this application, since there are base objects depending on it and it may resolve in issues on the site. If you don't intend using it, better to simply remove (hide) the sections from the workplaces instead of fully deleting it.

Mira Dmitruk,

We just have a situation that:



1. Our developing environment on-site is on 8.0.4

2. Customer test cloud environment is on 8.0.6

3. Customer production cloud environment is on 8.0.4



And there is object AccountAddress changed in 'Customer 360', but we cannot inhertit it cause otherwise our package will not work in production cloud. That gives us several issues



Kind regars,

Vladimir

I tried to uninstall this package on 8.0.6 because it impacted configuration I had previously made. Unfortunately we can't delete it. 

I am glad to have come upon this post!



Not that I am happy there is an issue, but you are avoiding us from doing a mistake. 8.0.6 does not seem the best Creatio version (albeit going in the right direction !)



Will refrain upgrading our on-premise clients past 8.0.5 until this is properly sorted out in 8.1.x (most probably will all the changes planned, 8.1.0 will not be properly ready either, and will wait for minor fixes first...)

Damien Collot,

1.1 is always better than 0.x :)

But here we have cloud

Vladimir Sokolov,

Could you please also specify the build of your systems?

Sales enterprise

I can see myself wanting to transition entirely to Creatio Studio. If all components that are used on OOTB sections/objects are available in the no-code designer, it feels like it's much better to start from scratch, given no customisation ends up like anything OOTB. 



I'm also hoping that there won't be performance issues for instances set up prior to 8.0.6 as it looks like so major changes of base packages on 8.1 forward

Yes this would be great ! :)

Hello,

 

Unfortunately, it can't be done via the standard export.  

Feed is absolutely another object in the system and there is no way to export feed using the standard export tool. 

But you can run this SQL query on your side (which is an example for the "Accounts" section) that will return feed messages for all accounts:



select a.Name Account_Name, a.Address Account_Address, sm.Message Feed_message from Account a inner join SocialMessage sm on sm.EntityId=a.Id



And then upload these feed messages from the DB.

If you have any further questions, please respond to this email we would be happy to help.

Thank you for choosing Creatio!

Hello,

It could be considered to create a List dashboard and select object Message/comment. Put necessary columns. From here then export in excel needed information. In Message/comment there are two columns that could be used to determine to what entity and record id, feed was posted: Schema and Object instance. The only thing is that these two columns provide Id, so to have some user friendly info additional manipulation in excel should be done. This is just alternative idea. 

BR,

Jelena

Hi, 

Information on the various CRM bundles available and an estimate generator can be found here: https://www.creatio.com/crm-pricing



The various licenses available for each Creatio bundle can also be found using the below links:

https://www.creatio.com/sales/pricing

https://www.creatio.com/marketing/pricing

https://www.creatio.com/service/pricing

Vishay Kerai,

Need more information on the licenses like customer journey license, creatio read only license  etc and its limitations

Hello Vladimir!

 

I will presume that you are using OOTB pages to provide you with an example of this logic.

 

The product has an Id and it is the same for system and portal users. The difference is only the edit page they see.

 

System user:

https://YOUR_WEBSITE.creatio.com/0/Nui/ViewModule.aspx#CardModuleV2/ProductPageV2/edit/b0e9bbd0-a818-4400-9163-d5a6a0e7aa9a

 

Portal user:

https://YOUR_WEBSITE.creatio.com/0/Nui/ViewModule.aspx#CardModuleV2/PortalProductPageV2/edit/b0e9bbd0-a818-4400-9163-d5a6a0e7aa9a

 

There how it is only different by the prefix "Portal" before the %Object%PageV2 part of the link. It is true for all OOTB sections.

 

With secure routing /ssp/ part is added after  "0":

https://academy.creatio.com/docs/developer/application_components/porta…

 

Example:

https://YOUR_WEBSITE.creatio.com/0/ssp/Nui/ViewModule.aspx#CardModuleV2/PortalProductPageV2/edit/b0e9bbd0-a818-4400-9163-d5a6a0e7aa9a

What I believe would be the best to use the business process to form links for portal users by using the first part of the link that is the same for all users and the id of the record (string+[macro]):

https://YOUR_WEBSITE.creatio.com/0/ssp/Nui/ViewModule.aspx#CardModuleV2/PortalProductPageV2/edit/[%Id%]

I hope my answer was useful to you.

Best Regards,

Dan

Hi,

There is a script that safely removes all duplicates in the table SysProfileData, you can use it:

delete

from "SysProfileData"

where "Id" in

  (

  select uuid(min("Id"))

  from "SysProfileData" 

  where "Key"<>'' and "Key"<>'chrome'and "Key"<>'gecko'

  group by "Key","ContactId", "SysCultureId"

  having count (*) > 1

  )

Hello,

It is indeed possible to calculate such value right inside of the forecast!

If you already have the "Opportunity amount" column in the forecast, you would need to do the following.

You would first need to add the "Probability, %" column to the forecast:

Notice that we have checked the "Hide column" checkbox since we do not want this column to be shown in the forecast table. If you want to edit it later, you can just add it back by clicking View -> List of columns:

After that, you need to add your calculated column:

Now you will be able to see the result after pressing the "Calculate" button!

On the screenshot below, the opportunity in the red rectangle has a probability of 50%, therefore the value in the calculated column is half of the real one:

Hope it helps!

Best regards,

Max.

Thank you for your clear reply. I thought of this, but it does not seem to work, as I want all those opportunities to be aggregated. So the calculation works on only one opportunity, but not when there are multiple opportunities, it seems because of the "sum" function on the calculation method. For example, I have 2 opportunities, assigned to 2 reps, so calculations work:

However, If I assign both opportunities to the same rep, then the % adds up to 130% and it seems to recalculate instead of just adding all the probable values:

The difference I have with your example is that I used the Contact section for my Forecast, to display sum by rep (it is a B2C use case, so accounts are irrelevant). So for that % probability, I am binding contact with opp owner, instead of doing it opp to opp like you are.

David Belanger-Goyette,

Unfortunately, the correct grouping value will be shown only if individual records are available in the forecast.

You can change the forecast to the following setup:

It will have the same structure, but will feature individual opportunities if you open contacts:

Best regards,

Max.

Thank you. I did not do it using the opp object because if the forecast runs on opportunity, then I will need to add all opportunities every time I want to check the forecast. I can add all opportunities now, but if new ones are created tomorrow, they will not show unless I manually add them. 

Hello Pedro!

Unfortunately, there is no way to achieve this with built-in instruments, as it is expected that there would be a different product record for each feature so that when adding them into orders you can determine exactly what feature set is required.

However, you can do this by creating a "Replacing view model" for the "SpecificationInProductPageV2" schema. There, you would only need to change the "validateSpecification" function by removing the following part:

After that, you will be able to add multiple features into products!

Best regards,

Max.

Hi,

Inside the OnSaving event, you can get a StackTrace of this event, however, you won't be able to distinguish at what object it was performed because the event itself starts from the same point.

To understand from where your activity was saved you can add a special column to it which will contain information about the save process and read it inside your OnSaving event.

For example, create a boolean column IsFromActivity page, set its default value to false and override method save() inside ActivityPageV2 and there set the value to true. Then inside OnSaving whit this column you can understand where this Activity was saved.

Hello,

Unfortunately, I didn't know a way to disable the checkbox on the lookup window and don't even know if that option is possible, however, in your case you can try a different approach. 

You can add a filter to an openLookup config that won't shop any records and disable it when you are using your config.selectedValues option.