Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0002971Openbravo ERP00. Application dictionarypublic2008-05-17 07:232008-06-12 09:43
Reporteruser71 
Assigned Tocromero 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version2.40alpha-r2 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0002971: Missing function call in ad_tab_import
DescriptionWhen creating window fields for a new tab (Application Directory->Tables,Tabs and Fields->Table->Tab) this operation failed with an error "AD_PInstance_Log.Log_ID can not be NULL". The reason is a missing call to AD_SEQUENCE_NEXT() in the database function AD_TAB_IMPORT. I have attached a patch to solve this problem.

Best regards,
Holger
Steps To Reproduce
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange

Notes
(0006560)
user71   
2005-06-01 00:00   
(edited on: 2008-06-12 09:43)
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis.

You can see the original bug report in:
https://sourceforge.net/support/tracker.php?aid=1965802 [^]
(0003687)
cromero   
2008-05-19 12:18   
(edited on: 2008-06-12 09:26)
Logged In: YES
user_id=1500614
Originator: NO

This doesn't report a bug but a problem with the installation/application. Please, use the forums to try to solve this problem.

Thank you very much.

Openbravo team
(0003688)
cromero   
2008-05-19 12:18   
(edited on: 2008-06-12 09:26)
Logged In: YES
user_id=1500614
Originator: NO

The problem is not in the AD_TAB_IMPORT function: the problem was originated before and for an unknown reason, the sequences was not properly set. So running the AD_UPDATE_SEQUENCE correct your problem with the AD_TAB_IMPORT but that no means that the problem was caused by that function.
(0003689)
psarobe   
2008-06-04 20:23   
(edited on: 2008-06-12 09:26)
Logged In: YES
user_id=1500703
Originator: NO

The bug was well reported and it is a bug. The problem is exactly where Holger Ebert says. This bug has been fixed removing that code from the procedure AD_TAB_IMPORT. There are another bug reporting in mantis for this