Export Map

[Sarah]

All,

I think I know why the code below doesn't work, but I wanted to make
sure before I give it up and try a different tack. Please advise.

MapEdit Name:="Map 1", Create:=True, OverwriteExisting:=True, _
DataCategory:=pjMapResources, CategoryEnabled:=True,
TableName:="OOTO_Report", _
FieldName:="Work Availability", ExportFilter:="*OOTO Monthly
Report"

 

[John]

Sarah,
"Doesn't work" is too general a phrase. Do you get an error message? How
exactly does it "not work"? From a pure syntax point, everything looks
ok. We need more information.

John

 

[Sarah]

John,

Well, I had the exact same map just above this one, but with a
different field name, and it compiled fine. I can't remember off-hand
exactly what the error was, but the only difference between the one
that "worked" and this one is the field name, so I concluded that was
the problem; that an export map won't accept that as a field, since
it's not one you can select to insert on the left pane.

Sarah

 

[John]

Sarah,
It sounds like you solved your own problem.
John

 

[Sarah]

John,

No, actually, I didn't. I was hoping someone would tell me that I
COULD use the field name "Work Availability", or something like it, in
an export map. It would make my life SO much easier at this point! ;-)
But I guess it's not possible?

Sarah

 

[John]

Sarah,
OK, now I understand. I apologize that I neglected to check that the
field name you want to use is valid. Work Availability is not a valid
Project field. Do you perhaps mean "Remaining Availability" as it
applies to the amount of time a resource is available? If so, this is a
timephased field and therefore cannot be exported with a simple export
map. You can however export Remaining Availability by using the "Analyze
timescaled data in Excel" add-in found on the "Analysis" toolbar. Run
the add-in from the Resource Usage view and select Remaining
Availability from the available fields in step 2.

If on the other hand you do indeed want "Work availability" you will
first have to define what it means. Then it may be possible to express
it in a spare field and export it using an export map. As a last resort,
ANY data derived from Project fields can be exported to Excel using a
VBA macro as long as an algorithm can be developed to define the data.

Hope this helps.
John

 

[Sarah]

John,

I do indeed mean Work Availability, and it is also a timephased field.
If you right click in the timescale portion of the Resource Usage view
and select Detail Styles, you can select Work Availability as a
timescale field. Remaining Availability does not work for me in a
shared resource pool environment, as I am trying to represent time out
of office per the resource calendars, and Remaining Availability is
relative to all linked projects' scheduled work for the resource. I
really need some way to export the Work Availability, which accurately
reflects resource calendars.

Thanks!
Sarah

 

[John]

Sarah,
Again I apologize. I thought I checked all the views for the Work
Availability field but I guess I missed it (I've obviously never used
the field myself).

Without digging too deeply into exactly what Work Availability
represents, it appears it is the sum of Work and Remaining Availability
per timescale period for a given resource. Given that, you should be
able to use the "Analyze timescaled data in Excel" add-in to export
those two fields to Excel and then apply the appropriate formula in
Excel to effectively get Work Availability.

If the above method doesn't give what you want, there is always the
custom VBA approach. With a custom macro, the TimeScaleData Method can
be used to export pjResourceWorkAvailability directly. This would be my
approach since it gives more control and flexibility.

Hope this helps.
John