product options

View: New views
6 Messages — Rating Filter:   Alert me  

product options

by Adam Heinz-3 :: Rate this Message:

| View Threaded | Show Only this Message

Background reading:

http://forum.vtiger.com/viewtopic.php?t=35611

I've worked around the color/size customization issues by adding
additional fields to vtiger_inventoryproductrel, but it seems somewhat
brittle.  I have started to dislike the vtiger_inventoryproductrel
table as a whole and would prefer to use a related module like
Assets... maybe some sort of editable related list view to preserve
the existing interface?  Moving to first class entities would increase
overhead a bit though, which I'm not keen on.

Has anyone else given this any thought?
_______________________________________________
http://www.vtiger.com/

Re: product options

by Prasad-14 :: Rate this Message:

| View Threaded | Show Only this Message

Adam,

vtiger_inventoryproductrel is a baggage carried forward ... re-structuring
or tweaking would take time as it is deep rooted with inventory modules.

We plan to achieve while building cleaner API framework at server.

Regards,
Prasad


On Thu, Apr 26, 2012 at 8:39 PM, Adam Heinz <amh@...> wrote:
Background reading:

http://forum.vtiger.com/viewtopic.php?t=35611

I've worked around the color/size customization issues by adding
additional fields to vtiger_inventoryproductrel, but it seems somewhat
brittle.  I have started to dislike the vtiger_inventoryproductrel
table as a whole and would prefer to use a related module like
Assets... maybe some sort of editable related list view to preserve
the existing interface?  Moving to first class entities would increase
overhead a bit though, which I'm not keen on.

Has anyone else given this any thought?
_______________________________________________
http://www.vtiger.com/


_______________________________________________
http://www.vtiger.com/

Re: product options

by Adam Heinz-3 :: Rate this Message:

| View Threaded | Show Only this Message

I'm making good progress on a prototype that allows rows in a related
module to be edited as part of the normal edit view.  I have created
new RelatedEditView.tpl and RelatedEditViewUI.tpl (inspired by /
cribbed from ProductDetailsEditView.tpl and EditViewUI.tpl
respectively) to allow me to have the following module hierarchy: an
order has a number of parts, each part is a product + additional
attributes.  This new parts module takes the place of
inventoryproductrel.

So far, so good.  The first wrinkle that I've encountered is
permissioning.  I'd  like to avoid having to propagate order ownership
to parts all the time, so I'm looking at doing something like "all
parts are owned by admin, but shared to the owner of the order".  I
believe that logic surrounds vtiger_datashare_relatedmodules, but I
don't see any existing code (other than the default data populator)
that inserts into that table.  I'm still running 5.2.1, is related
sharing something that I can rely on in the future?
_______________________________________________
http://www.vtiger.com/

Re: product options

by Alan Lord (News) :: Rate this Message:

| View Threaded | Show Only this Message

On 30/04/12 22:24, Adam Heinz wrote:
> I'm making good progress on a prototype that allows rows in a related
> module to be edited as part of the normal edit view.  I have created
> new RelatedEditView.tpl and RelatedEditViewUI.tpl (inspired by /
> cribbed from ProductDetailsEditView.tpl and EditViewUI.tpl
> respectively) to allow me to have the following module hierarchy: an
> order has a number of parts, each part is a product + additional
> attributes.  This new parts module takes the place of
> inventoryproductrel.

Hey Adam,

That sounds very encouraging!

I had a new enquiry yesterday with another use case for this feature...

The customer wanted to add a "cost price" and "margin" (auto calculated)
fields to the product module and have these displayed when they are
creating quotes (So they can see line-by-line, and as a total, the
margin on a deal). Obviously these extra fields are not to be printed on
the quote pdf ;-)

In this case the extra fields do [should?] not need to be edited when
building a Quote/Sales Order/Invoice. (A good use of the new "Read Only"
field feature in Profiles perhaps?)

I thought this was a good example of a use case and is also something we
have done with OpenERP implementations.

Cheers

Al


--
Libertus Solutions
http://www.libertus.co.uk

_______________________________________________
http://www.vtiger.com/

Re: product options

by Adam Heinz-3 :: Rate this Message:

| View Threaded | Show Only this Message

Long delay before I remembered to email about this, but I got my
related module edit view prototype working last week.  I'll work up
some screenshots and patches when I get a chance.
_______________________________________________
http://www.vtiger.com/

Re: product options

by Adam Heinz-3 :: Rate this Message:

| View Threaded | Show Only this Message

Ok, here's the screenshots I promised.  You can see that I have an
order form edit view that is a near mirror of the quote edit view.
You can add and delete order lines, etcetera, but the best part is
that since you are related against a real order line module, you can
configure the fields for that module and it changes the columns in the
related order form edit view.

The bad news is that I have no admin ui associated with this.  I do
all of my administration via vtlib scripts.  I'm still banging around
with the permissions issues mentioned earlier in this thread as well.
I'm also still figuring out how to get this working via the web service.

When it gets a little more finished, I hope to be able to contribute it
as a patch to vtlib/ModuleDir.  This is built in such a way so as not
to be specific to our custom module.  Comments welcome -- it is
still a work in progress.




_______________________________________________
http://www.vtiger.com/

orderform-detail.png (71K) Download Attachment
orderform-edit.png (64K) Download Attachment
orderline-edit.png (92K) Download Attachment