Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
|
Sorry, no photos available for this element of time.
|
|
Uploaded Media/Content & Other Files
(2)
|
||||
Media Name | File Type | Date | Description | |
disconnect_between_quote_lines_and_sub_total.jpg | Image/JPEG | 6/13/2017 | Small screen shot with a disconnect between the invoice total and the sub total based off of multi point decimals vs. the normal two decimal points for normal dollars. | |
a_new_customer_type_tax_filter.jpg | Image/JPEG | 6/13/2017 |
This is a small drawing to show how we could add a customer type filter to the taxing engine and tax calculations. Basically, some customer types need to be taxed and some don't. This is a way to add in the options to help the system know what to do. Also, by way of a note, what does the individual (per customer) tax setting do? |
Notes:
|
On the morning GoToMeeting session with Steve. I worked on adding some new code to help strip off the extra 0's on the adilas API sockets. We had a problem with a person submitting a number of zero padded id numbers. That was causing problems. While Steve and I were working on some of these simpler projects, we talked a lot about what we like and don't like inside of adilas. It has been quite the ride. After that, we talked about automating things and helping with some new tax calculations. We went over some new ways to limit a tax calc based off of a customer type. See attached for some ideas. Basically, we would add a new one-to-many filter option on the location and tax setting page. We would then make sure that we had a matching part category and matching customer type before applying the tax. At the end of the session, we had a client join us and show us a small rounding error on the quotes and the line items within a quote. We took some notes and told her we would look into it. The error seemed to be that we weren't recording the extended total (out to only 2 decimals). All of our math on the sub totals was still out at the 5 decimal places (quantity times price) and that was causing a small rounding error. See attached for a screen shot. |