 |
|
 |
| |
Please apply for Full Access if you want to report issues.
|
Viewing Issue Advanced Details
[ Jump to Notes ]
|
[ View Simple ]
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Reproducibility |
Date Submitted |
Last Update |
|
0010354 |
[CSVimp] All |
major |
always |
12-29-09 15:06 |
01-22-10 13:50 |
|
|
Reporter |
RUSSELL |
View Status |
public |
|
|
Assigned To |
gmoskowitz |
|
Priority |
normal |
Resolution |
no change required |
Platform |
|
|
Status |
resolved |
|
OS |
|
|
Projection |
none |
|
OS Version |
|
|
ETA |
none |
Fixed in Version |
|
Product Version |
|
| |
Product Build |
|
|
|
Summary |
0010354: 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 |
|
|
|
DocFlag |
False |
|
|
Attached Files |
|
|
|
 Relationships |
|
 Relationships |
|
Notes |
|
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. |
| |
|
Issue History |
|
Issue History |
|
Date Modified |
Username |
Field |
Change |
|
12-29-09 15:06 |
RUSSELL |
New Issue |
|
|
01-12-10 17:08 |
annecote |
Note Added: 0026793 |
|
|
01-12-10 17:08 |
annecote |
Status |
new => feedback |
|
01-12-10 17:08 |
annecote |
Description Updated |
|
|
01-22-10 13:50 |
gmoskowitz |
Status |
feedback => resolved |
|
01-22-10 13:50 |
gmoskowitz |
Resolution |
open => no change required |
|
01-22-10 13:50 |
gmoskowitz |
Assigned To |
=> gmoskowitz |
|
01-22-10 13:50 |
gmoskowitz |
Note Added: 0026946 |
|
|
|
 |
|
 |
