[
https://issues.apache.org/jira/browse/OFBIZ-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Imhof closed OFBIZ-987.
---
Resolution: Cannot Reproduce
Well, patching is getting more and more complicated for us because we
[
https://issues.apache.org/jira/browse/OFBIZ-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bilgin Ibryam updated OFBIZ-1176:
-
Attachment: pos.patch
the patch
POS order status error
--
On Monday 30 July 2007 12:24:13 am David E Jones wrote:
This is a good question... Right now these are mainly used for special
pages and we don't really have framework use of these yet, so I'd say at
this point we'll just have to see how things shake out!
The two main contenders in our
On Friday 20 July 2007 04:12:43 pm Jacopo Cappellato wrote:
Hi David (Shere),
I'd say we can store it in the PartyAttribute entity.
For example:
partyId=1
attrName=EBAY_BUYER_ID
attrValue=nY+sHZ2PrBmdj6wVnY+sEZ2PrA2dj6wGkYCnDZeHqQ+dj6x9nY+seQ==
I've used PartyContactMech for this
Ean Schuessler wrote:
On Monday 30 July 2007 12:24:13 am David E Jones wrote:
This is a good question... Right now these are mainly used for special
pages and we don't really have framework use of these yet, so I'd say at
this point we'll just have to see how things shake out!
The two main
Yes, it should work out. Thanks, Adrian.
Adrian Crum wrote:
Use 2 digit numbers in ALL of the IDs, so they can be compared correctly.
MrJohnBrown wrote:
If you have more than 9 entries it won't sort correctly. please, see the
picture:
Query is
select * from enumeration where
Products should have Roles just as ProductCategories and ProductCatalogs do
---
Key: OFBIZ-1177
URL: https://issues.apache.org/jira/browse/OFBIZ-1177
Project: OFBiz
