Best Of

... and make sure no-one and nothing other than the BC services modifies data in the BC database, except possibly for dedicated staging tables specifically created for that very purpose.

Compile all objects
Run Table Sync
Restart Nav Services

I don't understand what @Developer101 is saying.

Change log used to be triggered by the OnGlobal<Trigger> events (formerly procedures with pre-defined IDs in Codeunit 1. Those get triggered by user interactions in pages only. Modifications in code had to be logged by calling functions from within that code.

But after the OnDatabase<Trigger> events were introduced, any database operation which causes any record in the database to be changed triggers the logging.

Gotchas I am aware of:

• inserts for records with autoincrement fields do not record the correct value for that field, because the event is called with data from before the database insert operation (Edit: actually, I believe, before the database insert actually occurred. I could not find any way to find the missing value from within OnGlobalInsert (Auto increment fields are typically used as primary key)). I assume the same will be true for Timestamp fields, but I have not checked this out.
• the first updating database operation on a table triggers the event GetDatabaseTableTriggerSetup. Changes to the Change Log setup after this point will get active only after you start a new session. Changing the fields to be logged is not affected by this restriction.

I do have no experience with change log for fields defined in table extensions.

What is the page they getting this issue with?
Is it random or one specific page?
Change log only logs change in fields where data is entered and saved. If data is not saved in the fields then it wont record anything.

Use standard functionality and then you can use COPYLINK method.

Hi all,
i had a BC20 OnPrem envinronment with Windows Authentication that used Kerberos.
I upgraded it to BC24 keeping the same configurations (also for Kerberos) but now i cannot sign in to the web client because BC tell me that my user is an invalid user.




I am sure that the upgrade was succesfull because if i change the authentication method to NavUserPassword i can log in and i can see the migrated data correctly.


With the same configurations in BC20 everything worked correctly. I also tried to delete all users to be able to try to log in and then use the classic "Add me as administrator" on the users page but nothing, I always get the same type of problem.


Do you have any suggestion? Has anything changed from BC20 to BC24 from MS regarding the way delegations are configured?

Many thanks to anyone helps me.

Davide

Hi @ftornero
i managed to solve this issue.
Add content type must be added after writeform



Thanks.