Activities of "ageiter"

Okay, I have now recreated the scenario and attempted to reproduce the issue. However, it has now worked as intended and no entries were deleted from the database. I suspect that during my initial test, I made the change directly in the database and the cache had not yet been synchronized before I made the next change in the application.

Thanks for your help.

Unfortunately, we are unable to update at this time. Therefore, I would appreciate a response regarding how the framework behaves (in version 8.3.4). You may also simply confirm whether my following statements are correct or not.

• If the tenant has not assigned an edition and feature settings have been made on the tenant, these will persist when an edition is assigned (but the tenant will not receive the feature settings of the edition).
• When changing an edition on the tenant, all feature settings previously made on the tenant will be deleted.

However, my last two questions have nothing to do with the cache.

What can you say about that?

I have also identified a second problem. When I change the features of the assigned edition, the individual value of the tenant is deleted from the database and the value of the edition is applied.
It is very dangerous that settings are lost... is this the desired behavior?

Ok, thank you.

I now have the following problem:

1. Tenant does not yet have a subscription; I have set the maximum number of users there (as discussed above).
2. Customer has purchased a subscription, and the corresponding edition has been set.
3. Features of this edition were not activated.

Are no feature values of the edition applied as soon as a value is “overwritten” on the tenant? I assumed that only this value (Identity.MaxUserCount) differs from the values of the edition?

So you don't know how long the entries in the cache are valid by default?

I don't want to implement a special function for this individual case. If I did, I would have to override the standard behavior so that the field is not deactivated in the features on the tenant.

Are there any other ways to force synchronization (e.g., restarting the app)? Or does this happen regularly in the background as a job?

Oh, I guess it has something to do with synchronization in the cache. When I checked again after a while, the value I had entered in the DB was there.

What is the default frequency for DB and cache synchronization? Can this be forced?

Hmm... but I tried to achieve this on a experimental way by creating a corresponding database entry in the AbpFeatureValues table for this tenant. That didn't work, and the old value was still displayed in the UI.

Hi,

I already know that, unfortunately, I cannot configure any features on the tenant other than those in the assigned edition. This has already been communicated in the following post: #6579

Now I will describe our situation and I am interested to hear how you would resolve it.

We have various subscriptions (PayPlans, which are assigned to the editions). Depending on the subscription, the tenant gets a different number of maximum users. Identity.MaxUserCount is therefore set on the edition. Now, as an exception, we need to allow a higher number of users for one tenant.

What can we do? Unfortunately, the features cannot be overridden on the tenant. We don't really want to allow a higher number of users for the edition in general.

Could we create a new edition and assign it to the tenant? That would be a good solution. But since a subscription already exists, I cannot change the edition on the tenant (disabled in the UI). What would happen if I changed this in the database? And what effect would this have on subscription renewals, etc.?

Thanks, Adrian