Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 305 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Error while posting a journal with a particular project ref.
vamsi_praneeth
Member Posts: 23
Hi,
We are facing an issue whenever we are trying to post a General Journal with a project reference and date. It says "Cannot create a record in Expense(ProjCostTrans), 03-Apr-2011 Prj_0048. The record already exists". When I have checked if the date and project code is a unique index combination on the table, I found that there are many other entries with same project code and same date. Any help to resolve this issue is appreciated. I have cleared the usage data, synchronized the table and done all the regular stuff, but still this error is not getting resolved.
We are facing an issue whenever we are trying to post a General Journal with a project reference and date. It says "Cannot create a record in Expense(ProjCostTrans), 03-Apr-2011 Prj_0048. The record already exists". When I have checked if the date and project code is a unique index combination on the table, I found that there are many other entries with same project code and same date. Any help to resolve this issue is appreciated. I have cleared the usage data, synchronized the table and done all the regular stuff, but still this error is not getting resolved.
0