Issues with producing Published Maps

[ModernElectric]

Greetings-

    I have been having a lot of issues with producing .PMFs using ArcPublisher to have my maps used on ArcReader by my field crews. I have (2) different types of .PMFs that we use. The first one works fine - which is just a standard .PMF that I create by using the "Publish Map" tool. This .PMF sits on our internal network and able to be used by anyone connected to the network "In-House".

    The other one I call is a "Stand-Alone .PMF". The way I understand is I am able to create a .PMF or a "Map Package" and have the ability to take the whole folder and copy/move it a portable device (such as a laptop computer)
and open that .PMF on a laptop with ArcReader with No connection to the original Geodatabase. Here are some problems I am having with this:
      1) I have a few geodatabase tables that are "Joined" to a feature class. When I open the "Stand-Alone" .PMF those tables are no longer joined. What I mean is when I select a feature class and open the attributes in the Identiy Dialog box, only attributes for that feature class are present but not from the tables. ALSO - the symbols I created based on a specific attribute field are gone.
      2) On a few on my feature classes, I have the new Attachments feature enabled. In the "Network" .PMF all of those attachments are present. However, in the "Stand-Alone" .PMF - No Attachments. It still shows that something
is attached but the actual file is not there to be opened.

Any help or ideas on how to resolve these issues so I can properly load my data and maps onto a portable laptop?

Thank you

[TimHopper]

Chris,

You're running into two different things here.

1. Joins and relates are not supported when packaging the data with your published map.

Troubleshooting data packaging limitations

Packaging layers with ArcMap joins and relates topic.

2. The attachment issue is a bug.

NIM061515: When opening a packaged PMF in ArcReader, feature attachments are not viewable in the Identify window if the 'File Geodatabase', 'Compress File Geodatabase', and 'Compressed and Locked File Geodatabase' data formats were selected during the data packaging process.

The workaround for this bug is to select the "Copy data in existing format" on the General tab when packaging the data from the Publisher toolbar.

- - - - - - - -

My suggestion to you, in this situation, might be to use relative paths to your data and then send them the pmf along with data all in one folder.  The map will open, data sources intact, when opened on another computer.

Preparing maps for publishing

You store relative paths in the MXD, File > Map doc properties > Store relative pathnames to data sources.

Store all of your data in one windows folder, stick the pmf (unpackaged) in there, zip folder, and send.

[ModernElectric]

Chris,

You're running into two different things here.

1. Joins and relates are not supported when packaging the data with your published map.

Troubleshooting data packaging limitations

Packaging layers with ArcMap joins and relates topic.

2. The attachment issue is a bug.

NIM061515: When opening a packaged PMF in ArcReader, feature attachments are not viewable in the Identify window if the 'File Geodatabase', 'Compress File Geodatabase', and 'Compressed and Locked File Geodatabase' data formats were selected during the data packaging process.

The workaround for this bug is to select the "Copy data in existing format" on the General tab when packaging the data from the Publisher toolbar.

- - - - - - - -

My suggestion to you, in this situation, might be to use relative paths to your data and then send them the pmf along with data all in one folder.  The map will open, data sources intact, when opened on another computer.

Preparing maps for publishing

You store relative paths in the MXD, File > Map doc properties > Store relative pathnames to data sources.

Store all of your data in one windows folder, stick the pmf (unpackaged) in there, zip folder, and send.

Tim-

    Thank you for the information. I will work on the suggestions you gave me and see if they make a difference.

Dealing with the Data Packaging limitations of using Joins and Relates:
   Is there a work around for this or simply the Joins will not work. What about relationship classes?
   The data that I am using in these geodatabase tables are really critical. So - if I wanted to get the attributes from the tables directly into the feature class - what is the best way to do it? So initially - how do I go about getting the attributes into the feature class - NEXT when I need to update those attribute fields from an updated table - what is the best process for that?

Thanks again

[TimHopper]

Chris,

Published maps with relationship classes can be packaged with the copy setting. If the Intersect or Include All setting is used, the relationship class will not be packaged.

Joins and relates will not work with packaged pmf's, that's just the way it is unfortunately.

The difference with the relationship class is that you can identify a feature and get access to the related information, but it's not stored directly in the attribute table like the information from a join is.

If you're looking to permanently append the joined information, there isn't really any automated process for a workflow like that.

You can export the feature class that has a join from the Table of Contents (right-click > Data > Export Data).  The output feature class will have the joined data permanently appended.  When new data comes in (that is stored in the joined table) you would have to delete the fields with the joined info, rejoin, export.  You could create a model that does this for you (deletes fields, joins data, exports), but other than that you're pretty stuck.

Unless, of course, your underlying data never changes (just the joined data) which would allow you to join a new table to an older version of the feature class and export.

I might focus on trying to store relative path names in the mxd and then providing data + pmf to the laptop.

[ModernElectric]

Tim-

Again - thank you for the suggestions. I will experiment with some of these. One additional question: When I take a F.C. with a join from (2) geodatabase tables and export that out to make a new .SHP/FC - I will of course need to re import that into the geodatabase. The thing is - I will want to re import that in as the original name. Can I import that in and just override the FC name or do I have do delete it first and import it in second? The reason I ask is I have a few dozen relationship classes connected to this FC I am talking about.

Thanks