[
https://issues.apache.org/jira/browse/OFBIZ-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Vijaywargiya closed OFBIZ-2611.
--
Resolution: Fixed
Thanks Sumit!
Data committed at r788928.
--
Ashish
Add Posted and
[
https://issues.apache.org/jira/browse/OFBIZ-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Vijaywargiya reopened OFBIZ-2611:
Assignee: Ashish Vijaywargiya
Added new data file so opening this jira issue.
[
https://issues.apache.org/jira/browse/OFBIZ-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikas Mayur closed OFBIZ-2663.
--
Resolution: Fixed
Thanks Akash,
Your patch is in rev. 788929
Vikas
Supplier drop down list should
[
https://issues.apache.org/jira/browse/OFBIZ-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12724813#action_12724813
]
Hans Bakker commented on OFBIZ-2657:
Using the company email address is a bit difficult
This is a tough one since you would be moving from a less constrained
field to a more constrained one, ie a free-form field to a field with
an enumerated set of options. Doing an automated migration would only
work if you know that all current values in the database are among the
[
https://issues.apache.org/jira/browse/OFBIZ-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Vijaywargiya closed OFBIZ-2655.
--
Resolution: Fixed
Thanks Chirag.
Done at r788945.
--
Ashish Vijaywargiya
Portlet to
FYI - this may be the same issue I reported (OFBiz-2596). Problem with
CSS layout and elements not sizing (height width) as you would expect.
Ruth
Sumit Pandit (JIRA) wrote:
[
Steps to reproduce :
I tried derby database for installing ofbiz on trunk revision 788950 and
then ran command ant clean-all ant run-install.
I observed following error (Same error coming for external db i.e postgres):
[java] 2009-06-27 17:18:27,489 (main) [ DatabaseUtil.java:2754:INFO ]
Hi Rishi,
Hans can do a quick fix. I can tell you the problem, i.e indexing is
applied to infoName field of NoteData entity. And such field does not
exist. May be Hans wanted to apply indexing on noteInfo. Lets see What
Hans says.
Thanks
--
Divesh
Rishi Solanki wrote:
Steps to reproduce
should be ok now
On Sat, 2009-06-27 at 17:52 +0530, Divesh Dutta wrote:
Hi Rishi,
Hans can do a quick fix. I can tell you the problem, i.e indexing is
applied to infoName field of NoteData entity. And such field does not
exist. May be Hans wanted to apply indexing on noteInfo. Lets
Hi David,
On Jun 27, 2009, at 1:42 AM, David E Jones wrote:
This is a tough one since you would be moving from a less
constrained field to a more constrained one, ie a free-form field to
a field with an enumerated set of options. Doing an automated
migration would only work if you know
[
https://issues.apache.org/jira/browse/OFBIZ-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Vijaywargiya closed OFBIZ-2664.
--
Resolution: Fixed
Thanks Chirag!
Done at r788976.
--
Ashish Vijaywargiya
Portlet to
Add Csv and PDF generation functionalities to reporting type screens of
Accounting components.
--
Key: OFBIZ-2665
URL: https://issues.apache.org/jira/browse/OFBIZ-2665
[
https://issues.apache.org/jira/browse/OFBIZ-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12724861#action_12724861
]
BJ Freeman commented on OFBIZ-2657:
---
OK
in my implementatiion I use Company as the
[
https://issues.apache.org/jira/browse/OFBIZ-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Busco updated OFBIZ-2666:
---
Attachment: LargerPortletScreenshots.patch
Show a larger portlet screenshot
Show a larger portlet screenshot
Key: OFBIZ-2666
URL: https://issues.apache.org/jira/browse/OFBIZ-2666
Project: OFBiz
Issue Type: Improvement
Components: framework
Affects Versions: SVN trunk
Add C
-
Key: OFBIZ-2667
URL: https://issues.apache.org/jira/browse/OFBIZ-2667
Project: OFBiz
Issue Type: Sub-task
Reporter: Brajesh Patel
1.
[
https://issues.apache.org/jira/browse/OFBIZ-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brajesh Patel updated OFBIZ-2667:
-
Attachment: CSV_and_PDF_view_OFBIZ-2667.patch
Here I have attached patch for export search
On Jun 27, 2009, at 8:07 AM, Jacopo Cappellato wrote:
On a side note, would you want to do this with the suffix or any
other fields?
I am sorry but I don't understand the above question.
The questions was mainly for Bob, but I guess something for anyone to
consider: would we want to
I would say yes - but it does limit us to what we know about - but
that's the case with any lookup.
Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com
o:801.649.6594
f:801.649.6595
On Jun 27, 2009, at 11:32 AM, David E Jones wrote:
On Jun 27, 2009, at 8:07 AM, Jacopo
Yeah, that's the exact issue with the title too... there are
potentially thousands of them if you try to include every culture in
the world (and hundreds even for English speaking cultures, especially
if you include royalty/class titles, military titles, etc). On the
other hand, now that
Regd: 'Doing an automated migration would only work if you know that all
current values in the database are among the enumerated options you want to
migrate to'
Migration could check and create the enumerated option if it does not exist.
So Party has refrences to PersonalTitleId, where
Al Byers wrote:
Ean,
Could you please give a little more information about the type of content
and merges that you see in practice, so I can see if the CMS could be built
out to handle them?
Actually, storing these things in the database is not the best way to
go. It keeps people from
How about this proposal
1. Add enumeration id in addition to text field for these and any other
places where text could be replaced with reference. Some locations
(a) add Person::salutationTypeId references
PersonSalutionType:salutationTypeId
(b) add Person:personalTitleTypeId references
24 matches
Mail list logo
