Viewing Issue Advanced Details
ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
10354	[CSVimp] All	major	always	12-29-09 15:06	01-22-10 13:50
Reporter:	RUSSELL	Platform:
Assigned To:	gmoskowitz	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:
Product Build:		Resolution:	no change required
Projection:	none
ETA:	none
DocFlag:	False
Summary:	Export Import Errors
Description:	Exported contents from "Item List Master" to csv file. Tried to import the file as is into a new database and received the following error below: ERROR Record 1: ERROR: new row for relation "item" violates check constraint "item_sold_check" QPSQL: Unable to create query ERROR Record 2: ERROR: new row for relation "item" violates check constraint "item_sold_check" QPSQL: Unable to create query Thank you.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0026793) annecote    01-12-10 17:08	Russell, Are you still experiencing this issue? Where are you exporting from? Are you mapping the item sold field to the correct column in the item api view? In our item view this column is labeled "item_is_sold".
(0026946) gmoskowitz    01-22-10 13:50	This is not a bug. The CSV export feature in the xTuple ERP application dumps the displayed contents of the table view and is intended for import into other applications for further manipulation or presentation. It is not intended for dumping the entire contents of a table for loading another xTuple ERP database. Almost none of the displays in the xTuple ERP application contain enough data to meet the minimum requirements for their respective tables. In fact, many of the displays combine data from multiple tables and so there is no appropriate destination for their data.

Viewing Issue Advanced Details
ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
11487	[CSVimp] All	feature	always	06-01-10 10:34	06-09-10 14:51
Reporter:	Rydeljh	Platform:
Assigned To:	gmoskowitz	OS:
Priority:	normal	OS Version:
Status:	closed	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none
DocFlag:	False
Summary:	log of errors cannot be printed
Description:	Tool does not provide any method to print a log file when errors are received. When only 1 error type is shown it is not a big deal, however if you get errors on specific records when importing 15K of records it is nice to be able to print the log file out.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0031123) svn    06-08-10 13:44	Revision: 9454           http://postbooks.svn.sourceforge.net/postbooks/?rev=9454&view=rev [^] Author: gilmoskowitz Date: 2010-06-08 17:43:56 +0000 (Tue, 08 Jun 2010) Log Message: ----------- issue 0011487 - add ability to print contents of log window Modified Paths: --------------     csvimp/trunk/plugin/logwindow.cpp     csvimp/trunk/plugin/logwindow.h     csvimp/trunk/plugin/logwindow.ui
(0031136) mmcbride    06-09-10 14:51	verified fixed in 041

Viewing Issue Advanced Details
ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8807	[CSVimp] All	feature	always	05-08-09 12:54	12-31-09 19:09
Reporter:	jaufrec	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none
DocFlag:	False
Summary:	Use header information in CSV Atlas dialog
Description:	Steps to reproduce 1) Load a csv file with a header row in CSVimp 2) in the CSV Tool screen, click "Treat first row as header information" 3) Click Map -> Edit to bring up the CSV Atlas screen Actual Results 1) The Column # field has values such as Column 0, Column 1, Column 2 Expected Results 1) The Column # field is labeled something like "Source Column" and has as values the header information from the file, e.g., "City", "State"
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0026634) annecote    12-31-09 19:09	User would like to see column description in the drop down list with column number.

Viewing Issue Advanced Details
ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
11853	[CSVimp] All	block	always	08-06-10 11:00	08-06-10 11:02
Reporter:	joesingleton	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	confirmed	Product Version:	0.4.2
Product Build:		Resolution:	open
Projection:	none
ETA:	none
DocFlag:	False
Summary:	csvimp login window does not allow enhanced authentication
Description:	The options to use Enhanced Authentication and require SSL are no longer available in the login options window for CSVImp. see forum posting @ http://www.xtuple.org/node/3324 [^]
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0032213) gmoskowitz    08-06-10 11:02	This was an unintended consequence of revising CSVImp to be available within the xTuple ERP app.

Viewing Issue Advanced Details
ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
11516	[CSVimp] All	feature	always	06-03-10 12:36	06-03-10 12:37
Reporter:	Daniel	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none
DocFlag:	False
Summary:	allow feeding results of the pre-sql query to the actual import phase
Description:	It would be nice if CSVImp allowed using data returned by the Pre-SQL query as part of the import. For example, a query could return an internal cohead_id for a given Sales Order number. Then this internal id could be used when importing coitem records. This would also allow reading default settings from the database.
Steps To Reproduce:
Additional Information:
Attached Files:

There are no notes attached to this issue.

Viewing Issue Advanced Details
ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
9581	[CSVimp] All	minor	always	09-10-09 12:53	09-16-09 10:57
Reporter:	j2m	Platform:
Assigned To:	ptyler	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none
DocFlag:	False
Summary:	Link to Import Documentation incorrect
Description:	The link: http://www.xtuple.org/ImportingData [^] does not go to the importing data instructions. It points to Event Management instead.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0024229) ptyler    09-16-09 10:57	Great feedback. Thanks! This is fixed now. Page wasn't ported properly during website migration in the spring.

Viewing Issue Advanced Details
ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7069	[CSVimp] All	feature	N/A	07-29-08 14:30	07-29-08 14:46
Reporter:	nordic	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	closed	Product Version:	0.4.2
Product Build:		Resolution:	open
Projection:	none
ETA:	none
DocFlag:	False
Summary:	csvimp and API Views - General Questions
Description:	I have two specific questions and two general ones. Specific questions: s1. Using csvimp, can I do the equivalent of what an SQL Update query does? s2. Using csvimp, can I do the equivalent of what an SQL Delete query does? General question: g1. Can I run an SQL Update query that uses an API view to reference the underlying data in tables? g2. Can I run an SQL Delete query that uses an API view to reference the underlying data in tables? --Mike Rosemire, on behalf of Nordic Naturals
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0015410) jrogelstad    07-29-08 14:46	Mike, Please post support questions on the xTuple forums or by sending e-mail directly to support. The issue tracker is used only for reporting bugs or feature requests. Kindest Regards, John

Viewing Issue Advanced Details
ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
11658	[CSVimp] All	block	always	06-23-10 21:29	06-30-10 08:43
Reporter:	carolyn	Platform:	Manufacturing
Assigned To:	cryan	OS:	ALL
Priority:	normal	OS Version:	ALL
Status:	resolved	Product Version:	0.4.1
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none
DocFlag:	False
Summary:	All Items not Imported - no errors in log
Description:	When trying to import Items, no errors were reported, but all rows were not imported. On the first attempt, 3000 of Items were imported and 1700 failed although no errors were logged. On the second attempt, only 1061 rows were imported and again, no errors were logged. When the same file was imported using 0.3.0 all 4700 rows imported without incident. On the third attempt (using the csv and atlas I created and successfully imported with version 0.3.0) 3800 rows were imported and the rest were ignored.
Steps To Reproduce:
Additional Information:
System Description	xTuple ERP Manufacturing Edition
Attached Files:

Notes
(0031587) mmcbride    06-24-10 08:36	are you using the api views or the table? Is this for database version 351RC?
(0031589) carolyn    06-24-10 08:58	using API and 3.5.1rc
(0031692) svn    06-30-10 08:42	Revision: 9583           http://postbooks.svn.sourceforge.net/postbooks/?rev=9583&view=rev [^] Author: cryan Date: 2010-06-30 13:11:57 +0000 (Wed, 30 Jun 2010) Log Message: ----------- Issue 0011658. Fixed problem where some records were not imported when running large imports. Modified Paths: --------------     csvimp/trunk/plugin/csvtoolwindow.cpp

Viewing Issue Advanced Details
ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
9497	[CSVimp] All	major	always	08-23-09 17:51	01-29-10 19:16
Reporter:	brook	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	closed	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none
DocFlag:	False
Summary:	Product category field "not found" error while running csvimp (api.item)
Description:	ERROR Record 1: ERROR: Product Category not found. QPSQL: Unable to create query
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0023921) gmoskowitz    08-24-09 08:50	Strictly speaking the error message is true: there is no field called "Product Category". There /is/ a field called "product_category" (note the underscore between words). Which version of the column name did you give csvimp?
(0026612) annecote    12-31-09 12:49	Reminder sent to: brook Ok to close this issue?
(0027072) annecote    01-29-10 19:16	Closed due to lack of feedback

Viewing Issue Advanced Details
ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
5801	[CSVimp] All	feature	always	09-10-07 10:40	09-10-07 13:32
Reporter:	jrogelstad	Platform:
Assigned To:	jrogelstad	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none
DocFlag:	False
Summary:	Allow the ability to select schema
Description:	CSV Imp defaults to the public schema. Allow user to select a schema so they can get to API views. Perhaps add a command line switch to force a schema selection so it could be launched from PostBooks/OpenMFG and not have to worry about uneducated users importing directly into public tables?
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0011917) jrogelstad    09-10-07 13:32	----------- 5801: Allow CSV imp to see and use api schema. Modified Files: --------------     CSVimp:         CSVimp.pro (r1.10 -> r1.11)         csvatlaswindow.ui.h (r1.15 -> r1.16)

Viewing Issue Advanced Details
ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
11517	[CSVimp] All	feature	always	06-03-10 12:40	06-30-10 09:06
Reporter:	gmoskowitz	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none
DocFlag:	False
Summary:	integrate the metasql editor from openrpt to edit the pre- and post-import queries
Description:	It might be helpful to be able to test the pre- and post-import queries when editing them. The MetaSQL editor from OpenRPT allows this.
Steps To Reproduce:
Additional Information:
Attached Files:

There are no notes attached to this issue.

Viewing Issue Advanced Details
ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
3171	[CSVimp] All	text	always	01-25-05 21:57	08-03-10 14:53
Reporter:	chrisking	Platform:
Assigned To:	gmoskowitz	OS:	Mac OS X Panther
Priority:	normal	OS Version:
Status:	resolved	Product Version:	0.4.2
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none
DocFlag:	False
Summary:	field type incorrect in field mappings window
Description:	When viewing a table inside the mappings definition window, QString will be displayed as the type when it should be "char(1)". This makes it difficult to map fields.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0032105) svn    07-28-10 16:13	Revision: 9761           http://postbooks.svn.sourceforge.net/postbooks/?rev=9761&view=rev [^] Author: gilmoskowitz Date: 2010-07-28 20:13:47 +0000 (Wed, 28 Jul 2010) Log Message: ----------- bug 0003171 - show max string length in field mappings if available Modified Paths: --------------     csvimp/trunk/plugin/csvatlaswindow.cpp
(0032106) gmoskowitz    07-28-10 16:15	The field type will show as QString(5) if the field is limited to 5 characters and the database driver permits. Text fields with unrestricted length will still show as QString.

Viewing Issue Advanced Details
ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
3172	[CSVimp] All	feature	always	01-25-05 21:59	01-26-05 13:45
Reporter:	chrisking	Platform:
Assigned To:		OS:	Mac OS X Panther
Priority:	high	OS Version:
Status:	confirmed	Product Version:	0.4.2
Product Build:		Resolution:	open
Projection:	none
ETA:	none
DocFlag:	False
Summary:	add comment ability to field mappings
Description:	it would be very useful to be able to annotate individual fields as one proceeds with a migration. This annotation could then either be put into the table comments, or just saved on the client side inside the mapping file.
Steps To Reproduce:
Additional Information:
Attached Files:

There are no notes attached to this issue.

Viewing Issue Advanced Details
ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
9685	[CSVimp] All	major	always	10-06-09 10:47	06-09-10 14:52
Reporter:	matherton	Platform:	OpenMFG
Assigned To:	gmoskowitz	OS:	ALL
Priority:	high	OS Version:	ALL
Status:	closed	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none
DocFlag:	False
Summary:	CSVimp only enables access to public and api schemas
Description:	CSVimp does not enable access to views such as xtmfg, xtpos, xtbatch and customer created schemas.
Steps To Reproduce:
Additional Information:
System Description	xTuple ERP Manufacturing Edition
Attached Files:

Notes
(0029559) malfredo32    04-07-10 20:45	You can add to this issue that you can't access xtmfg either and in consequence you can't import BOO's. Alfredo
(0031122) svn    06-08-10 13:09	Revision: 9452           http://postbooks.svn.sourceforge.net/postbooks/?rev=9452&view=rev [^] Author: gilmoskowitz Date: 2010-06-08 17:09:15 +0000 (Tue, 08 Jun 2010) Log Message: ----------- bug 0009685 - allow selecting any table or view from any non-system schema Modified Paths: --------------     csvimp/trunk/plugin/csvatlaswindow.cpp     csvimp/trunk/plugin/plugin.pro Added Paths: -----------     csvimp/trunk/plugin/csvaddmapinputdialog.cpp     csvimp/trunk/plugin/csvaddmapinputdialog.h     csvimp/trunk/plugin/csvaddmapinputdialog.ui
(0031137) mmcbride    06-09-10 14:51	verified fixed in 041

Viewing Issue Advanced Details
ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
11691	[CSVimp] All	feature	always	06-30-10 09:05	06-30-10 09:06
Reporter:	cryan	Platform:
Assigned To:		OS:
Priority:	low	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none
DocFlag:	False
Summary:	Standalong CSVimp does not use transactions -- should when database supports requirements
Description:	When performing large imports the use of savepoints in transactions can easily lead to memory problems. Newer (8.4.1 and up?) versions of postgresql are supposed to address this problem. If this is the case the transaction support should be added back in with a conditional use when on a version of postgresql that does not exhibit the shared memory leak problem.
Steps To Reproduce:
Additional Information:
Attached Files:

There are no notes attached to this issue.