AAI

Why can I not get a Detailed Lined Item report by Location and by Zone or by Zone only???

I don’t want reports that are by Category, it produces very long reports for the client. Am still relying on the legacy reports.

The wire issue I had at the very beginning of the release has still not been resolved, I reported this issue in the beta program and have reported it twice to support! I am having to change the length of wire I need and the pricing on the report afterwards. I believe this issue is only for the UK users. Should you not have considered UK users as well when releasing SI5?????

D-tools is suppose to reduce time for the business and so far we have spent far too much time on it already trying to overcome all the bugs etc.

RickC

Originally Posted by AAI

Why can I not get a Detailed Lined Item report by Location and by Zone or by Zone only??? I don’t want reports that are by Category, it produces very long reports for the client. Am still relying on the legacy reports.

Reports can have zero or more report definitions. Report Definitions control how the data is grouped, sorted, and the settings of parameter values.

One of these definitions should have the "Default Definition" flag set (it's a checkbox on the form). This setting means when a user selects a report in the Reports List, the report will generate against this definition. If a user selects a specific definition, the report will generate based on these settings.

I think it could be one of three things:

1. A defintion that groups by category is selected as the default.
2. You have a definition named something that does not represent its actual settings. The name of the defintion has nothing to do with how it works. It's simply organizational meta data that is completely user defined.
3. No definitions are selected as a default (it doesn't sound like this is the issue though).

Take a look that the document linked below. It goes into some detail about report definitions and should help you get through the problem you are seeing.

Report Definitions

Originally Posted by AAI

The wire issue I had at the very beginning of the release has still not been resolved, I reported this issue in the beta program and have reported it twice to support! I am having to change the length of wire I need and the pricing on the report afterwards. I believe this issue is only for the UK users. Should you not have considered UK users as well when releasing SI5????? D-tools is suppose to reduce time for the business and so far we have spent far too much time on it already trying to overcome all the bugs etc.

While I am not directly involved in the solution for this particular issue, I can tell you that it is a priority issue being addressed in the next SP which is currently in testing and while a release date has not been set, we are working to get this out there as soon as possible.

-R

RandyB

Originally Posted by AAI

The wire issue I had at the very beginning of the release has still not been resolved, I reported this issue in the beta program and have reported it twice to support! I am having to change the length of wire I need and the pricing on the report afterwards. I believe this issue is only for the UK users. Should you not have considered UK users as well when releasing SI5?????

As Rick mentions in his post, we are currently testing the fixes for this, which will be in Service Pack 3 due out soon. We will be sending out more information about this late next week or early the week of the 8th since it involves fundamental changes to the way metric projects are stored.

I can tell you that the following issues have been identified and fixed:

1. When measurement units = metric, the unit price, unit cost, unit labor hours and length of wires in projects is calculating incorrectly, particularly for finish wires or wires in a package.

2. When measurement units are changed in the Navigator from Metric to US or vice versa, the unit cost, unit price and unit labor hours for finish wires are being converted upon display in MMPD (Product Grid, Product Properties)

3. Reports show wire lengths, unit prices, and product dimensions in feet rather than in meters for metric projects

4. Wire lengths and unit prices are rounded since the data is stored in feet. This has been corrected in projects (however not in the product database), allowing for greater precision.

We sincerely apologize for the delay. This turned out to be a fairly complex issue but the fix is on the way.

Best regards,

Randy