View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003316 | OXID ERP Interface | OXID ERP Interface - sub | public | 2011-10-17 15:36 | 2013-01-21 12:39 |
| Reporter | Stefan_Werner | Assigned To | |||
| Priority | high | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 2.8.0_31492 | ||||
| Target Version | 2.9.0_35501 | Fixed in Version | 2.11.1_54476 | ||
| Summary | 0003316: OXERPSetArticle ingnores values for OXPARENTID | ||||
| Description | If you use OXERPSetArticle on an existing article and replace the value for oxparentid with empty the former value will not change, the old parentid is still inserted. | ||||
| Tags | No tags attached. | ||||
| related to | 0004678 | resolved | aurimas.gladutis | OXID eShop (all versions) | Article can not be converted to variant |
|
|
Reminder sent to: Stefan_Werner Hi, Could you describe the case in more details why you need such behavior, to set empty oxparentid value (=unset the variant from parent-product)? As in eshop there is no such functionality, like making usual products from variants. Basicaly for that you need to delete variant product and create new product in usual way. Please tell us about your business case. |
|
|
Hi, we have exacly the same case in one of our Projects. The Case is: We dont generate own oxids, they are given by ERP. If the customer wants to split the article variants in single Products he has to remove the parentid on the given product. As we cant build a own, new product with own oxid we have to overwrite the variant. our fix was to completely overwrite the: function _skipSaveFields() of oxarticle and we commented out the line: $this->_aSkipSaveFields[] = 'oxparentid'; in my opinion, the check for a emtpty or not set parentid ist not needed in any place of the shop. |
|
|
Other use case of that request: "An ERP business partner found this Issue during the switch from summer to winter collection, according to them they often change the assignment of articles/variants because of the changing category architecture." |
|
|
After internal discussions we decided to implement the fix for that issue as separate method in ERP module for setting oxparentid. This will help to avoid cases, when data is corrupted because oxparentid is not delivered by mistake. Also the fix in eShop also will be needed to support that functionality. |
|
|
oxparent = '', reset parent |
