Finance | Project Operations, Human Resources, ...

Imported a Record into databaselog table not showing in Database log setup form in d365 F&O

(1) Share

Report

Posted on by charanch

106

HI All,

We have around 1000 records in the Database Log Setup form in AX 2009, and we want to migrate those records to the Database Log Setup form in D365 Finance & Operations.
To achieve this, we created a custom data entity in D365 FO by adding the DatabaseLog table as the data source. Yesterday, I tested importing one record through this custom entity, and the import was completed successfully.

During the import, I provided the following values in Excel:
TableName
TableId
LogType
FieldName (left empty)

After the import:

The record is visible in the backend DatabaseLog table (verified through SSMS).
However, the record is not appearing in the "Database Log Setup" form in the application.

1.I researched why the record was not appearing in the form, I learned about the "Consistency Check" button in the Database Log Setup form. It is used to synchronize data if any records are left as orphaned. I executed this option, but the record still does not appear in the form.
2.I also debugged the code while opening the Database Log Setup form, but everything seems to be working fine.
Could anyone please suggest whether I might be missing any link or if I need to update any additional related tables for the record to appear correctly in the Database Log Setup form?
3.Are TableName, TableId, LogType, and FieldName sufficient fields for the data entity, or should I include additional fields to avoid future reference issues during import?

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (4)

Answers (0)

Diego Mancassola 684 on at

Like (0)

Report
Copy link

Link copied!

Hello, i never do that, may another expert can has the solution for you.

But, only thinking about it, if anyone request me a task like this, i try to create the log from code and not pushing data using a data entity.

In my approach i'll try to find if there are a X++ code to enable the log from code, than not create data directly in table, but enable the log by code using a job to import data from 2009.

I think using this class Microsoft.Dynamics.Ax.Xpp.SysDatabaseLog.SysDatabaseLogManager you can enable the log on table, in particular EnableDbLog().

Hope experts doing this has the answer.

Was this reply helpful? Yes No
Martin Dráb 238,789 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!
Don't speculate whether the form doesn't use inner joins or so - instead, look at the actual query. Open Database log setup for, right-click it, choose Form information > Form name: SysDatabaseLogSetup and check the Query statement field.

This is the result in my environment:

SELECT FIRSTFAST FORUPDATE * FROM DatabaseLog(DatabaseLog) USING INDEX Loglist WHERE ((logType = 0) OR (logType = 2) OR (logType = 1) OR (logType = 3))

As you see, SysDatabaseLogSetup form (unless customized) doesn't have any joins with other tables that would exclude your record; but it has a filter on LogType. Have you used one of the supported log types?

Regarding your list of fields, I don't think you should populate the able ID from AX 2009. Use TableName and FieldName as entity fields (mapped to LogTableName and LogFieldName) and use them in code of your data entity to find IDs (that you'll put to LogTable and LogField fields).

Was this reply helpful? Yes No
charanch 106 on at

Like (0)

Report
Copy link

Link copied!

Hi Martin ,

I have imported a record with logtype - 'Insert' and yes, from ax2009 I am not getting any Table Id for that I used some code to get table Id based on table name while inserting.
But still not able to understand why, the record is not showing in the database log setup form.

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 303,397 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Charanch,

Can you tell what you are logging in the application and for what reason? 1000 setup records is insanely high. Do you have a process to review the logs and cleanup the logs regularly?

Note that if you are running Dynamics 365 in the cloud, there are limitations to the size of your storage, depending on the number of licenses.

To come to your questions.

1) The consistency check is not repairing data without additional logic. It is scanning for inconsistent data storage.

3) The table ID in Dynamics 365 can be different from the Table ID you had in AX2009.

Was this reply helpful? Yes No