the two entity id's are different for same Address entity
If your address entity has a navigation property and the change made in the related property, this might be the reason for that.
Yes, We are already enabled and all the audits are getting in to the tables but how we will know that belongs to which entity? In which table that entity relationship will found.
In the audit logging page, you can switch to the Entity Change tab and see the details.
Ok thank you waiting for your feedback.
Our QA team will test it today and I will write you back asap. Thanks for understanding.
Hi, you need to enable entity history and then it will save entity changes for the relevant entities and the EntityId column will be filled with the changed entities Id.
Please refer to the documentation: https://abp.io/docs/latest/framework/infrastructure/audit-logging#entity-history-selectors
If your Blazor Server app is hosted on a different domain than the embedding page (HTML/Azure Power Apps), the browser might block the request due to CORS (Cross-Origin Resource Sharing) restrictions.
So, you need to modify the cors configuration (and define the related CorsOrigin) - update your appsettings.json file -:
{
"App": {
"CorsOrigins": "https://*.MyProjectName.com"
}
}
Check https://abp.io/docs/9.0/solution-templates/layered-web-application/cors-configuration for more info.
Hi Engincan, I missed that part in the document. Issue solved. Thank you very much for your support.
Hi, great to hear that, thanks.
Regards.
Hi, I will check and let you know asap.
Regards.
Hi, the encryption of the Client Secret in ABP’s External Provider settings is a security measure designed to protect sensitive authentication credentials. Storing client secrets in plaintext poses a significant security risk, especially if unauthorized users gain access to the database or configuration files. Encrypting them helps prevent exposure in case of data leaks or misconfiguration.
Regards.
Hi, emailing settings are retrieved through the ISettingManager service, which caches data internally. Most likely, the old values you saw were due to cached data.
Now that you've updated the settings again, the cache should be invalidated, allowing the latest values from the database to be used and re-cached. You shouldn’t encounter this issue again.
Regards.
I removed the log out thing, still same issue. I believe that the Identity Module Pro is capturing the user normally but not deleting it.
Hi, there might be a problem as you stated. Our qa team will test this scenario and I'll let you know.
Regards.
Hi, when you update language texts, the changes are made by the host user (tenantId: null). However, these changes are not inherited by other tenants. This behavior is intentional, as it ensures that data remains tenant-specific. Therefore, you need to manually update the text template values for each tenant.
Regards.
