Stump the Panel

Paul Grenier, Lead Moderator

Stump the Panel » Site Managers and Site Collection Managers

1. 

   [email protected]
   Member

   We host an ASP.NET website (we created a subsite with publishing features enabled) for our Intranet users within a Site Collection of "Team Portals." On the site we have two flash applications -- a migration map and a timeline -- that are totally dynamic and are generated from XML files stored in a Document Library on the site.

   For this to work in our situation, I need to develop an administrative tool that will allow the content managers to edit the XML and SAVE it back to the Document Library. Since the raw XML is not user-friendly to these users, I have to load the data into form components to allow them to edit in a way that makes sense to them and then translate those changes back to the XML that the Flash use. (for example, the XML node is mStatus and the XML saves either Blue, Orange, Green, or Purple -- the display colors. But to the senior managers, they would want a pull-down with choices of Active, Pending, Planning, ToBeConfirmed.)

   I first tried to use InfoPath but it mangles the XML and breaks the Flash.

   I then tried Flex 3 and Flash CS4 to build the tool and hand off the XML to a php page for saving on the remote server but PHP is not on the remote server.

   I do not have access to develop and deploy a Visual Studio feature so I could not use .NET to save the file.

   I have no idea what to do because there are so many obstacles in place. Flash or Flex can't save a file, the IT won't authorize a feature, etc, etc.

   Can someone give me a direction to head in this -- to save (and replace) an existing XML file in a Document Library.

   Thanks in advance for your time,
   Jon

   Posted 1 month ago #
2. 

   AutoSponge
   Administrator

   Here's what I would try.

   1. Setup the attributes for the XML in a SP List (works easily as long as you don't have repeating child elements--with repeating children, it can work but takes some more effort, see below).

   2. Fire up SPD and create a DVWP (if you have children to join, use a joined data source).

   3. Make the DVWP render your XML as you would see it in an editor.

   4. Change the header's content type: ContentType="text/xml".

   When you serve the custom aspx page, it will render your data and tell the browser/consuming app/page the content is text.

   Posted 1 month ago #

RSS feed for this topic

Reply

You must log in to post.