Aaron Keating - Lipsey's, LLC
My feedback
26 results found
-
1 voteAaron Keating - Lipsey's, LLC
shared this idea
·
-
1 voteAaron Keating - Lipsey's, LLC
shared this idea
·
-
6 votesAaron Keating - Lipsey's, LLC
supported this idea
·
-
3 votesAaron Keating - Lipsey's, LLC
supported this idea
·
-
5 votesAaron Keating - Lipsey's, LLC
supported this idea
·
-
4 votesAaron Keating - Lipsey's, LLC
supported this idea
·
-
3 votesAaron Keating - Lipsey's, LLC
supported this idea
·
-
4 votesAaron Keating - Lipsey's, LLC
supported this idea
·
-
4 votesAaron Keating - Lipsey's, LLC
supported this idea
·
-
2 votesAaron Keating - Lipsey's, LLC
supported this idea
·
-
4 votesunder review ·
AdminEdward M. Kwang - NETcellent System, Inc.
(CEO / Founder, NETcellent Systems, Inc.)
responded
This project is declined because to export notes in export processor will result in poor performance because we do not use index in Export Processor. On the other hand, the Report Desk in Elliott 8.6 can be used to print or export notes to CSV or xlsx. So that's a better solution for a generic notes export function.
Aaron Keating - Lipsey's, LLC
shared this idea
·
-
2 votesAaron Keating - Lipsey's, LLC
shared this idea
·
-
2 votesAaron Keating - Lipsey's, LLC
shared this idea
·
-
13 votes
An error occurred while saving the comment An error occurred while saving the comment Aaron Keating - Lipsey's, LLC
commented
Add item boxed height, width and length into item file for future use. The volume field does not give an accurate representation of the item to calculate DIM weights or determine packaging in any future enhancements.
An error occurred while saving the comment Aaron Keating - Lipsey's, LLC
commented
With the new additional fields being added, the Sales Desk Screen layout also needs to be expanded to have more than 12 custom fields displayed.
An error occurred while saving the comment Aaron Keating - Lipsey's, LLC
commented
While changing the table structures, I think it would beneficial add these 2 pieces of information for reporting purposes.
Customer Type should be recorded on the invoice header at the time of posting. This gives an accurate representation of what the customer's type was at the time of the sale. Joining the customer table to the invoice header only tells you what the customer's type is now, not what it was at the time of order.
The starting source of a sale should be recorded on individual line items. The source would be where the order originated from. Online, API, custom specified, etc... This would need to be on the order line item and then carried over to the invoice line item. Then, you could create very accurate historical reporting on order entry sources. Having this information on a note attached to the invoice header or line item is cumbersome and could be deleted. With this method, once the line item is added, the source is saved forever. This source field could also be carried over to the CPHSTTRX table. The actual source field only needs to be a few characters and each company can decide their own code formats.
An error occurred while saving the comment Aaron Keating - Lipsey's, LLC
commented
Is it safe to assume that Elliott v8.x can continue to run in production and V9 can be run concurrently from a separate database for testing?
I don't see anyone being able to switch over cold to v9, especially considering all of the breaking table changes and adjustments and testing that needs to happen to all reports, websites, etc...
Also, will there be new VIEWS made available to merge all of the data that is separating back together for easy querying?
-
3 votesAaron Keating - Lipsey's, LLC
supported this idea
·
-
3 votesAaron Keating - Lipsey's, LLC
supported this idea
·
-
3 votes
An error occurred while saving the comment Aaron Keating - Lipsey's, LLC
commented
FYI - this is still an issue.
Aaron Keating - Lipsey's, LLC
shared this idea
·
-
3 votesAaron Keating - Lipsey's, LLC
shared this idea
·
-
4 votesAaron Keating - Lipsey's, LLC
supported this idea
·
-
3 votesAaron Keating - Lipsey's, LLC
supported this idea
·
Item packaging Length, Width and Height should be added to the item file as well. This could be used for future use in the WMS and other external applications