Stump the Panel

Paul Grenier, Lead Moderator

Stump the Panel » End Users and Information Workers

1. 

   baldcat
   Member

   Ok so got a good one..

   One of the dev guys needs to be able to write a report using SQL reporting that can show any entry than has had the "Due Date" changed ..

   So have a list and lets say it is a task list.. When first created the "Due Date" is 24-11-2008. This is reported on at the monthly meeting as a task that will completed this month.. During the next month meeting the report is run and it is there again..as the due date has changed to 24-12-2008 during the month.
   Exec what a report on "What" tasks have changed Due dates..

   So is there a way to captcha this data ?? I was thinking auditing, policy type thoughts but really haven't much to do with this gear as we haven't really put into place "YET"

   Posted 3 months ago #
2. 

   baldcat
   Member

   http://www.aussieslivingsimply.com.au/images/Untitled-picture.jpg

   Ok so in versioning, I can see the two diferent dates.. Does any one know where I can go and grab that data ?

   Posted 3 months ago #
3. 

   Dessie Lunsford
   Moderator

   One thing you could look at is how versioning is stored in the URL's for the items.

   For a "Tasks" list (with the default of versioning enabled for each edit), the URL for each new version has an number added to it that is incremented in values of 512.

   Examples:

   An item on the list as version 6.0

   The current version (6.0) will appear as: /Lists/Tasks/DispForm.aspx?ID=1
   Version 5.0 will be: /Lists/Tasks/DispForm.aspx?ID=1&VersionNo=2560
   Version 4.0 will be: /Lists/Tasks/DispForm.aspx?ID=1&VersionNo=2048
   Version 3.0 will be: /Lists/Tasks/DispForm.aspx?ID=1&VersionNo=1536
   Version 2.0 will be: /Lists/Tasks/DispForm.aspx?ID=1&VersionNo=1024
   Version 1.0 will be: /Lists/Tasks/DispForm.aspx?ID=1&VersionNo=512

   (You can see these URL's by clicking on version history in the edit dropdown for the list item and hovering over each version's link)

   Since these "512-increments" are always consistant, one option would be to use JavaScript to parse the URL for the current item, then based on its version number, dynamically create the URL's for each of the previous versions (you'll know how many to create and the numbers to append, based on the current version number), then (possibly) use JavaScript to crawl these "Created" URL's and parse the HTML on each page to grab the "Due Date" values.

   I'm by no means a JavaScript guru, and I'm not sure how to approach this (what the script would entail), but it may be possible.

   Question for fellow Moderator:

   Paul, can you chime in here on the feasability of this? Can you do an "HTTP Request" through JavaScript to follow a URL, parse the resulting html on multiple pages, then produce the results for each "Due Date" value on a new page...or something similar? Any other ideas on how to get the data from previous versions?

   - Dessie

   Posted 3 months ago #
4. 

   AutoSponge
   Administrator

   I was looking into version data before I left for vacation but didn't have anything to report yet. I'll add this to favorites and look into it when I get back. To answer your other question directly, getting data from a URL is essentially the same thing the JavaScript API does (which I wrote about in pt5 of my series this month).

   Posted 3 months ago #

RSS feed for this topic

Reply

You must log in to post.