gnichols

When I try running a Client report (be it Proposal Summary, or Proposal Summery with Images), a number of items are being reported as being in "Unassigned" locations, when in fact they are assigned when you look at the project in SI Text.

I've look at the .DTL file (it is XML afterall and none of the items show as UNASSIGNED in the xml file. Where is the report writer getting its data from and why are things showing up as Unassigned?

Yesterday, I also had the instance of items showing up in a report (for the same client) that had been in past revisions, but were not currently in the project. What's going on here?

Is there anything I can do to get this to work propoerly?

Thanks.

./griggs

RickC

Reports running out of the reporting center generate their directly against the project DTL file. The DTL file is transformed via an XSLT document into the XML file the report is run against.

When an item in the report has a location = "Unassigned", the location node in the DTL looks like:

<dtp:Location xsi:nil="true" />

so you can search on that to determine if there are items that are, in fact, not assigned to a location.

As far as items showing up from a previous revision, as the report data is generated directly against the DTL file, my guess would be that either the report was generated against the revision or the items are somewhere in the DTL.

-R

gnichols

Originally Posted by RickC

When an item in the report has a location = "Unassigned", the location node in the DTL looks like: <dtp:Location xsi:nil="true" /> so you can search on that to determine if there are items that are, in fact, not assigned to a location.

Super... All well and good... I found the nil="true" items...

I guess this begs a larger question -- Why are items that are showing up in SI Text view as having been assigned a location, coming into the XML as <dtp:Location xsi:nil="true">?

Any ideas?

Thanks!

./g

RickC

Originally Posted by gnichols

Super... All well and good... I found the nil="true" items... I guess this begs a larger question -- Why are items that are showing up in SI Text view as having been assigned a location, coming into the XML as <dtp:Location xsi:nil="true">? Any ideas? Thanks! ./g

Not really sure on this. Are these items in a package? If so, is the package set to allow items into different locations? If so, it may be that the PDM is grouped in such a way that the items are associated with a package (in a location), but the items themselves are not. This is pure guess though.

I'd suggest funnelling this through support if what I suggested isn't the case.

-R

gnichols

Originally Posted by RickC

Are these items in a package?

As a matter of fact, they do appear to be in a package!

Originally Posted by RickC

If so, is the package set to allow items into different locations? If so, it may be that the PDM is grouped in such a way that the items are associated with a package (in a location), but the items themselves are not. This is pure guess though. I'd suggest funnelling this through support if what I suggested isn't the case.

hmmm... The check box is checked to allow the equipment in the package to be in a different Location/Zone, HOWEVER all of the equipment is showing (in the SI Text view) as having been assigned to the same LOCATION.

Here's where it might be going wrong tho -- the package's "default" (grayed out) location is showing "_Unassigned".

I'll try unchecking the box, adjusting that, and then rechecking the box.

It seems like there might be some sort of "disconnect" going on...

Thanks for pointing me in the right direction. I'll get back to you on the end result.

./griggs

gnichols

Originally Posted by gnichols

I'll get back to you on the end result.

That took care of it!

I unchecked the box, re-assigned the Location and Zone, then rechecked the box.

Thanks!

./g

RickC

Originally Posted by gnichols

That took care of it! I unchecked the box, re-assigned the Location and Zone, then rechecked the box. Thanks! ./g

Excellent. What's happening is that the Proposal groups be top level item (Package in this case). The to get the actual locations of the equipment in the package, you need to run a line item detail report (this explodes packages and deals with the individual items) or you can right a "Package Detail" report of some sort.

The data and breaking were correct, just not what you initially expected.

Glad we found the answer. Thanks for the follow up.

-R