View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005694 | OXID ERP Interface | OXID ERP Interface - sub | public | 2014-03-13 13:16 | 2024-10-09 08:47 |
Reporter | michael_keiluweit | Assigned To | |||
Priority | normal | Severity | major | Reproducibility | always |
Status | confirmed | Resolution | open | ||
Product Version | 2.12.0 | ||||
Summary | 0005694: OXERPSetArtExtends does not support language set tables | ||||
Description | If a shop has more than 7 languages, the shop creates automatically set tables. For example: oxarticles contains oxtitle, oxtitle_1, oxtitle_2, ... oxtitle_7. For the eighth language, the column oxtitle_8 is located in oxarticles_set1, which was created by the shop. The ERP method OXERPSetArtExtends does only set the values for language 1 - 7. The eighth language is ignored. | ||||
Steps To Reproduce |
| ||||
Additional Information | .xml files aren't allowed, so added .txt to the name. | ||||
Tags | Internationalization Rework, Mass Data import, Product domain and basket rewrite | ||||
Attached Files | oxsetarticle.xml.txt (1,997 bytes)
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:oxer="OXERPService"> <soapenv:Header/> <soapenv:Body> <oxer:OXERPSetArticle> <oxer:sSessionID>j0pbe0jd5hbger4l3ki1uqnht3</oxer:sSessionID> <oxer:aArticle> <oxer:OXERPType> <oxer:aResult> <oxer:ArrayOfString> <oxer:string>OXID</oxer:string> <oxer:string>05833e961f65616e55a2208c2ed7c6b8</oxer:string> </oxer:ArrayOfString> <oxer:ArrayOfString> <oxer:string>OXTITLE_1</oxer:string> <oxer:string>foo</oxer:string> </oxer:ArrayOfString> <oxer:ArrayOfString> <oxer:string>OXTITLE_2</oxer:string> <oxer:string>bar</oxer:string> </oxer:ArrayOfString> <oxer:ArrayOfString> <oxer:string>OXTITLE_8</oxer:string> <oxer:string>blafusel</oxer:string> </oxer:ArrayOfString> <oxer:ArrayOfString> <oxer:string>OXLONGDESC_1</oxer:string> <oxer:string>foodesc</oxer:string> </oxer:ArrayOfString> <oxer:ArrayOfString> <oxer:string>OXLONGDESC_2</oxer:string> <oxer:string>bardesc</oxer:string> </oxer:ArrayOfString> <oxer:ArrayOfString> <oxer:string>OXLONGDESC_8</oxer:string> <oxer:string>blafuseldesc</oxer:string> </oxer:ArrayOfString> </oxer:aResult> <oxer:blResult>1</oxer:blResult> <oxer:sMessage></oxer:sMessage> </oxer:OXERPType> </oxer:aArticle> </oxer:OXERPSetArticle> </soapenv:Body> </soapenv:Envelope> oxsetartextends.xml.txt (1,411 bytes)
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:oxer="OXERPService"> <soapenv:Header/> <soapenv:Body> <oxer:OXERPSetArtExtends> <oxer:sSessionID>j0pbe0jd5hbger4l3ki1uqnht3</oxer:sSessionID> <oxer:aArticle> <oxer:OXERPType> <oxer:aResult> <oxer:ArrayOfString> <oxer:string>OXID</oxer:string> <oxer:string>05833e961f65616e55a2208c2ed7c6b8</oxer:string> </oxer:ArrayOfString> <oxer:ArrayOfString> <oxer:string>OXLONGDESC_1</oxer:string> <oxer:string>foodesc2</oxer:string> </oxer:ArrayOfString> <oxer:ArrayOfString> <oxer:string>OXLONGDESC_2</oxer:string> <oxer:string>bardesc2</oxer:string> </oxer:ArrayOfString> <oxer:ArrayOfString> <oxer:string>OXLONGDESC_8</oxer:string> <oxer:string>blafuseldesc2</oxer:string> </oxer:ArrayOfString> </oxer:aResult> <oxer:blResult>1</oxer:blResult> <oxer:sMessage></oxer:sMessage> </oxer:OXERPType> </oxer:aArticle> </oxer:OXERPSetArtExtends> </soapenv:Body> </soapenv:Envelope> | ||||
|
Maybe the method OXERPSetArtExtends can be removed anyway, because all the functionality of it is given with the method OXERPSetArticle which works fine. Reason: We do have two tables for the article, but from the outside we have just one article object which holds the information. And this object should be used in any case to avoid more maintenance work. |
|
ERP interface objects match eShop database tables for supported objects (articles, categories, vendors and etc.), that is why OXERPSETARTEXTENDS is there. In addition, oxERPType_Artextends class wraps OXTAGS fields which are not included in oxERPType_Article. |
|
This is still valid, oxartextends does not have a MultilanguageModel (it has no Model at all). So from eight language on no data is inserted for OXERPSetArtExtends. I wouldn`t suggest to remove this method completly, because OXERPSetArticle handles only LONGDESC properly and not custom data fields. One way to solve this problem in project scope is to introduce a dummy-oxartextends-Multilanguage Model and use this for object oxERPType_Artextends. |