Aaron Keating - Lipsey's, LLC

My feedback

  1. 3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aaron Keating - Lipsey's, LLC supported this idea  · 
  2. 4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aaron Keating - Lipsey's, LLC supported this idea  · 
  3. 2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aaron Keating - Lipsey's, LLC supported this idea  · 
  4. 1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aaron Keating - Lipsey's, LLC shared this idea  · 
  5. 5 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aaron Keating - Lipsey's, LLC supported this idea  · 
    Aaron Keating - Lipsey's, LLC commented  · 

    This would be extremely helpful. Also add Statement Frequency Code.

  6. 2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aaron Keating - Lipsey's, LLC supported this idea  · 
  7. 3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aaron Keating - Lipsey's, LLC supported this idea  · 
  8. 2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  0 comments  ·  Elliott Forum  ·  Admin →
    Aaron Keating - Lipsey's, LLC supported this idea  · 
  9. 11 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    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.

    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.

    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.

    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?

  10. 1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aaron Keating - Lipsey's, LLC shared this idea  · 
  11. 3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aaron Keating - Lipsey's, LLC commented  · 

    FYI - this is still an issue.

    Aaron Keating - Lipsey's, LLC shared this idea  · 
  12. 2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aaron Keating - Lipsey's, LLC shared this idea  · 
  13. 4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aaron Keating - Lipsey's, LLC supported this idea  · 
  14. 3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  Elliott Forum  ·  Admin →
    Aaron Keating - Lipsey's, LLC supported this idea  · 
  15. 3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aaron Keating - Lipsey's, LLC shared this idea  · 
  16. 3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aaron Keating - Lipsey's, LLC supported this idea  · 
  17. 2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aaron Keating - Lipsey's, LLC supported this idea  · 
  18. 3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aaron Keating - Lipsey's, LLC supported this idea  · 
  19. 3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aaron Keating - Lipsey's, LLC supported this idea  · 
  20. 2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aaron Keating - Lipsey's, LLC supported this idea  · 
    Aaron Keating - Lipsey's, LLC commented  · 

    A good example would be the GetOneItemDetail method in the iteminquiry.asmx web service. It returns the attributes associated with an item. Let's say you have an attribute set up called MANUFACTURER that uses the System code values to create the dropdown box in the Attribute and standardize the input. You could have a value of "MT" set up with a value description of "Motorola" for the MANUFACTURER attribute. When you query the GetOneItemDetail web service for an item with that attribute, it will return the value "MT" for the MANUFACTURER attribute in the ATTRIB_REF_1 value in the XML return. The value description is not returned, but it is most likely the value you would want to display on a website, POS system, etc... as MT is not descriptive enough. Sometimes, you can fit the entire word in the value key, but it is only 15 characters and that is not always an option.

    Aaron Keating - Lipsey's, LLC shared this idea  · 

Feedback and Knowledge Base