Skip to main content

Notifications

Announcements

No record found.

Finance | Project Operations, Human Resources, ...
Suggested answer

DB sync issue after upgrade from 33 to 10.0.0.39

Posted on by 9
I did a version upgrade from .33 to 10.0.0.39 (10.0.1860.56) and now facing the errors below after full DB sync. Anyone faced the same issue or has any idea how this can be probably fixed. 
 
I have two VMs and both have the same issue.
 
Severity    Code    Description    Project    File    Line    Suppression State
Error        Log level - Error | Infolog diagnostic message: 'Specified datasource CustInvoiceTransLineChargesTaxAmountView of View BundleSalesInvoiceLineEntity is a temp table.' on category 'Error'.            0    
 

Error        Log level - Error | Infolog diagnostic message: 'Specified datasource BundleSalesInvoiceBundleLineChargesTaxAmountView of View BundleSalesInvoiceBundleParentLineEntity is a temp table.' on category 'Error'.            0    
 
Thanks for the help guys.
  • Ehtisham Shaikh Profile Picture
    Ehtisham Shaikh 9 on at
    DB sync issue after upgrade from 33 to 10.0.0.39
    Hello Peter,

    The trade/charges config key is already enabled on my system.
  • Ehtisham Shaikh Profile Picture
    Ehtisham Shaikh 9 on at
    DB sync issue after upgrade from 33 to 10.0.0.39
    Hello Navneeth,

    Thanks for the reply.
    I cannot access the link you provided and the answer to both of your questions is no.
     
  • Suggested answer
    Navneeth Nagrajan Profile Picture
    Navneeth Nagrajan 1,439 Super User 2024 Season 2 on at
    DB sync issue after upgrade from 33 to 10.0.0.39
    Hi ES-04061354-0,
     
    For this issue
    Severity    Code    Description    Project    File    Line    Suppression State
    Error        Log level - Error | Infolog diagnostic message: 'Specified datasource CustInvoiceTransLineChargesTaxAmountView of View BundleSalesInvoiceLineEntity is a temp table.' on category 'Error'.            0    
     
    References:
    Disabling the Markup configuration key will address this issue as mentioned in the link below.
     
     
    Error        Log level - Error | Infolog diagnostic message: 'Specified datasource BundleSalesInvoiceBundleLineChargesTaxAmountView of View BundleSalesInvoiceBundleParentLineEntity is a temp table.' on category 'Error'.            0    
    There are new functionalities categorised under the Bundles model in D365 SCM.
     
    Questions :
    1. Has this model been referenced in your custom model (if any) while upgrading. After upgrade you can choose to not reference this model if there is no dependency on Bundles?
    2. Are any of the sales invoices referencing voided sales orders etc.?
     
     
     
  • Suggested answer
    DB sync issue after upgrade from 33 to 10.0.0.39
    Hi, this is a known issue, I faced the same. It will be fixed in PU 10.0.41. Until that comes you can turn the following configuration key on to eliminate the DBSynch error: Trade/Charges.
     
    Hope this helps,
    Best regards,
    Peter Prokopecz
    info@daxvisionerp.com
     
  • Ehtisham Shaikh Profile Picture
    Ehtisham Shaikh 9 on at
    DB sync issue after upgrade from 33 to 10.0.0.39
    I cannot adjust any code because this is inside [Bundle] model and I have not extended it either.
  • CU05060451-0 Profile Picture
    CU05060451-0 2 on at
    DB sync issue after upgrade from 33 to 10.0.0.39
    The errors you're seeing indicate that there's an issue with temporary tables. In SQL Server, #temp tables are session-specific, while ##temp tables are global. If the system is expecting a global temp table and finds a local one, this could cause the error you're seeing. You may need to adjust your code to ensure that the correct type of temp table is being used https://stackoverflow.com/questions/1265525/sql-server-shows-invalid-object-name-temp-when-working-with-a-temporary-tab house of hazards    
  • Layan Jwei Profile Picture
    Layan Jwei 7,345 Super User 2024 Season 2 on at
    DB sync issue after upgrade from 33 to 10.0.0.39
    Hi,
     
    I remember that In some projects i used to always get this 'category' error (but different error than yours). I just ignore it and it doesn't affect my working.
    Maybe it was related to ISV solution.
     
    Thanks,
    Layan Jweihan
    Please mark this answer as "Verified" if it solved your issue. In order to help others who will face a similar issue in the future

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,253 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,188 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans