someone can help me. please, i need group the sizes of configurable products in one row in the shopping cart
something like this.
http://i.imgur.com/BfqndNz.png
Related
This is a basic customer card:
As you can see there is a "Salesperson" linked to the customer, but in many situations customers can have multiple salespersons.
In this field I can only select one salesperson.
The problem created by this situation in the company is that sales people can't find customers that are not linked to them.
How can I assign multiple salesperson to customers?
If your salespeople are in fixed groups e.g. person A and B handle the same group of customers and C and D handle another group of customers, you could use the Responsibility Center feature.
Create a Responsibility Center for each group of customers and assign it to those customers. Then set the Sales Resp. Ctr. Filter on the User Setup for each Salesperson.
Using this field, obviously, you can't. You need to use some other field like department or customer group I don't know. Or if I remember correctly the was a table like ’My Customers’ where every user can build a list of customers he's interested in.
I am using xcart classic 4.7.1 for my shop. We did a lot of customization in the code to make it suitable for my clients need. We made it live the previous year and everything worked fine. Now, these days a strange issue is happening. The products are randomly appearing and disappearing in the cart. Sometimes after adding the products to cart, the cart stays empty. It is not happening regularly. Sometimes if a product is deleted from the cart, previous products are randomly added into the cart again. Suppose the cart containing 4 products. Customer deleting the products one by one. After he deleted the last product, previously deleted products are showing in the cart again. As it is not happening regularly, it is very hard to track it and fix it. A lot of customers are complaining and my client is not happy now.
Thank you very much in advance. Blessings.
1)Try to convert the engine type from MyISAM to InnoDB for the xcart_sessions_data table.
For this
run the query
ALTER TABLE xcart_sessions_data ENGINE=INNODB;
2)Maybe upgrade to the newest X-Cart version will fix the problem.
Since there has been a lot of customization in your cart, as you wrote, the most probable reason is some bug in the customizations, related to the cart functionality. Have you had any customizations on the cart functionality itself?
I want to create a small app that creates a kind off receipt record in to a db table, from two other tables. very much like a receipt from a grocery store where a cashier makes a sell and the ticket contains multiple items, calculates a total and subtotal and return values to the database. I currently have 3 tables: the Ticket table where i would like to insert the values of all calculations and ticket info, the services table that acts like an inventory of services available. this has the service name and price for each service and my responsible table that has a list of "cashiers" or people that will make the sale and their percentage for their commissions, i have the views to create , edit and delete cashier's and services.
What I don't have is a way to create the ticket. I am completely lost. can you guys point me in to the correct path on what to look for. i am learning to program son i don't have a lot of knowledge in this if its even possible. i don't need the system to print i just want to have all record stored this way later on i can expand on it and create reports of sold items and who sold them and how much commissions each seller has won.
You need to create relationships to two other models (tables) from the Ticket model (table). Luckily you don't have to create the relations in the database tables itself. Use django model's Foreign key fields to accomplish this. Here is the documentation link:
Django Models
You may need to read it several times to get the concepts thoroughly.
Using ForeignKey relationships, I want to be able to copy data and store it in another model. For example, think of how you would handle past Invoices and billed Services.
The Invoice would have one or more Services associated with it and with prices for the Services. This prices for a Service can / will change over time - but the Service price recorded with the Invoice should remain as it was when the Invoice was created.
My first thought was to create a pdf from the resulting data and store it. But this would make the data somewhat inaccessible.
Is there somehow a way to copy the data and keep them accessible?
This is a pretty broad problem with multiple solutions. I dont think that what you're aiming to is the correct one.
One rule for saving invoices is, that invoices never change. You should never update an invoice. So not only your 'copies' of invoices should remain the same, but the original too.
Also, you should have a InvoiceItem (or InvoiceRow) model which are the items on your invoice. Don't bind Products to a Invoice directly.
Here are 2 solutions I've used:
Solution 1
You can normalize the data on your invoice(items). So, don't use foreignkeys, but normalize all data about the product, so product info (incl. price) is saved within the invoice(item).
Solution 2
Give your products revision numbers. So everytime a product is updated (name or price change for example), a new product is created in the database. Now you can link the InvoiceItem to a Product with a Foreign Key, and it will will be historically accurate.
Im sure there are some guides/best practices for creating Invoice backends. Language or Framework is not important. Invoicing is really important, so do alot of research before starting to build something. That's just my two pennies
I am working on some tagging infrastructure for my client. There is need to have tagging for the following - Regions, Countries, Cities and Office Locations.
Items in the content tree can be tagged for only region, country or city. But there also needs to exist relationship between the above tags as follows
Regions --> Countries --> Cities --> Office Locations.
The relationship between cities and office locations can be many to many.
I can pursue the above relationship by having 4 separate lists - one each for regions, countries, cities and offices.
Then I can follow two modes of tagging
EITHER
On the Office tag item, there can be a multilist field for a city tag and multiple cities could be selected that way for an office. Then the city tag can have a multilist field for selecting countries, and country tag can have a multilist for regions. The region item would not have any fields.
OR
A region tag can have a multilist field to select countries, a country tag can have a field to select cities, a city can have multilist field for offices, and offices won't have any fields.
Which method is preferable and why?
I do not want to do a hierarchical structure as that would not sit well with many to many relationship issue.
Thanks
If I understand your situation, it feels like the second (top-down) approach is the one you should go with.
I'd do it for a couple of reasons:
In your first option, you mention an Office would have a multilist for multiple cities. Would an Office location really have multiple cities? I would think that an office location should only have a single city associated with it, which would point me to the top-down approach.
The top-down approach just makes more sense logically. Look at the way you described your tagging relationship:
Regions --> Countries --> Cities --> Office Locations.
You're already describing it that way and I think it would make more sense to then architect it that way as well.