RSS

Category Archives: Office

20 Cool Features that make OneNote 2007 ROCK!

So here are the 20 features that makes OneNote 2007 ROCK!  Some of these are kind of repetitive in concept so I’ll boil those down to a more "main concept" post later.  So without any further adieu, here are the 20 features that make it ROCK!
  1. Live Session Sharing – Allows geographically disparate users to whiteboard together i.e. work on the same note pages at the same time.
  2. Tables – The addition of tables makes it possible to highlight tabular information more precisely than before.
  3. Calculator – Write up any calculation and end it with an = sign.  Press SPACEBAR and vuala OneNote automatically fills in the answer for you.
  4. Drawing Tools – OK, so this is why OneNote is so much more useful with a tablet PC than a laptop.  Nobody is going to be drawing with a mouse, but a pen is an entirely different story.
  5. Templates – You can now turn pages into templates so if you like to customize your starting page, you can do so.
  6. Video Recording – On top of the audio recording that you were able to do before, you can now also record video.  The indexed notes mean you can simply select a note you took during the recording to jump directly to the location in the video/audio file.
  7. Drag & Drop Page Organization – Easily rearrange your pages by simply dragging them from their current location and dropping them where you want them to be.
  8. Hyperlinks – Link to any URL.
  9. Encryption – Tab sections can be assigned password which then encrypts the content using 3DES for security.
  10. Multi Computer Sync – Edit the same workbook from multiple computers and OneNote will sync when it’s connected.
  11. Mobile – Now support for mobile devices.
  12. Quick Side Notes – Instead of launching OneNote, the system tray icon now launches a quick note window.  The quick notes are collected in a grouping in OneNote.
  13. Web to OneNote – Using Tools/Send to OneNote in IE you can send entire web pages, even just the selected text to a OneNote Quick Note.
  14. OCR – Using any image that you past into a note, right click the image and select "Copy Text from Image".  The clipboard now contains the text and it can be pasted anywhere.
  15. OneNote Printer – A special printer is added to your printer list that enables you to print anything directly to OneNote.  Once in OneNote, you can annotate and edit over the top of the printout.
  16. Send to Word – OneNote content can be sent to Word.
  17. PowerPoint Integration – You can insert PowerPoint slides into OneNote and annotate over the top.
  18. Excel Integration – The addition of tables allows you to copy any table from Excel and past it to OneNote.
  19. File Attachments – Any files can be attached and edited from a page.
  20. Lasso – This is kind of a free hand selection tool.  It allows you to select ink content and move it around the page.

Later
C

 

Advertisements
 
11 Comments

Posted by on May 28, 2006 in Office

 

InfoPath treating fields as protected…

While working on a InfoPath/SharePoint/BizTalk solution, I ran into a strange oddity.  The solution basically takes HL7 data feeds in BizTalk and then using the WSSLib adapter it writes the record to a Windows SharePoint Services based form library.  Users then interact with the data in the form library via the InfoPath form.  Simple right…

So while conducting my testing I found that some of the fields are protected.   In this case I was able to see both the WorkPhone field and the WorkPhoneExt field, but I was only able to update the WorkPhone field.  Now what is up with that???

OK, so obviously the schema definition of the fields in question must be different from the other surrounding fields that do work right.  Take a look at the schema and see if you can spot the problem…

 

<?

xml version="1.0" encoding="utf-16"?>

<

xs:schema xmlns:b="http://schemas.microsoft.com/BizTalk/2003&quot; xmlns:xs="http://www.w3.org/2001/XMLSchema"&gt;

  <xs:element name="PAS_Record">

    <xs:complexType>

      <xs:sequence>

        <xs:element minOccurs="0" name="EventCode" type="xs:string" />

        <xs:element minOccurs="0" name="MedicalRecordNum" type="xs:string" />

        <xs:element minOccurs="0" name="RegNum" type="xs:string" />

        <xs:element minOccurs="0" name="PreRegNumber" type="xs:string" />

        <xs:element minOccurs="0" name="LastName" type="xs:string" />

        <xs:element minOccurs="0" name="MaidenName" type="xs:string" />

        <xs:element minOccurs="0" name="FirstName" type="xs:string" />

        <xs:element minOccurs="0" name="MI" type="xs:string" />

        <xs:element minOccurs="0" name="SSN" type="xs:string" />

        <xs:element minOccurs="0" name="DOB" type="xs:string" />

        <xs:element minOccurs="0" name="Gender" type="xs:string" />

        <xs:element minOccurs="0" name="PrimaryLanguage" type="xs:string" />

        <xs:element minOccurs="0" name="Race" type="xs:string" />

        <xs:element minOccurs="0" name="MaritalStatus" type="xs:string" />

        <xs:element minOccurs="0" name="Address" type="xs:string" />

        <xs:element minOccurs="0" name="City" type="xs:string" />

        <xs:element minOccurs="0" name="State" type="xs:string" />

        <xs:element minOccurs="0" name="Zip" type="xs:string" />

        <xs:element minOccurs="0" maxOccurs="unbounded" name="Telephone">

          <xs:complexType>

            <xs:sequence>

              <xs:element minOccurs="0" name="HomePhone" type="xs:string" />

              <xs:element minOccurs="0" name="HomePhoneExt" type="xs:string" />

              <xs:element minOccurs="0" name="WorkPhone" type="xs:string" />

              <xs:element minOccurs="0" name="WorkPhoneExt" type="xs:string" />

            </xs:sequence>

          </xs:complexType>

        </xs:element>

      </xs:sequence>

    </xs:complexType>

  </xs:element>

</

xs:schema>

 

Well can you spot it?  Don’t feel bad if you weren’t able to identify the problem.  I didn’t see it either… because it wasn’t there!!!  Note these comparisons:

        <xs:element minOccurs="0" name="RegNum" type="xs:string" />

<<<works…>>>

        <xs:element minOccurs="0" name="PreRegNumber" type="xs:string" />

<<<fails…>>>

type="xs:string" />

        <xs:element minOccurs="0" name="Race" type="xs:string" />

<<<works…>>>

        <xs:element minOccurs="0" name="PrimaryLanguage"

type="xs:string" />

<<<fails…>>>

              <xs:element minOccurs="0" name="HomePhone" type="xs:string" />

<<<works…>>>

              <xs:element minOccurs="0" name="HomePhoneExt" type="xs:string" />

<<<fails…>>>

              <xs:element minOccurs="0" name="WorkPhone" type="xs:string" />

<<<works…>>>

              <xs:element minOccurs="0" name="WorkPhoneExt" type="xs:string" />

<<<fails…>>>

 

OK, since the form was derived from simply dragging the schema onto the canvas, maybe the fields got defined different somehow.  So I proceeded to check the properties of each of the InfoPath edit boxes for the fields in question as well as surrounding fields.  Here’s the properties comparison between RegNum and PreRegNumber displaying a snapshot of each pane first for RegNum then for PreRegNumber:

 

Data tab

 

 

Display tab

 

 

Size tab

 

 

Advanced tab

 

So did you notice any difference?  Well, neither did I.  OK, so we’ve eliminated schema differences… we’ve eliminated form property differences… what is going on here?

So I posted to microsoft.public.infopath because surely there’s an InfoPath MVP genius out there who knows the answer right?  

No takers… Nothing… Nada… Zip… Zigalo… Didley Squat!

Mmm… guess I’m on my own on this one… so I started playing around a some more.  At home that night I was not connected to corporate VPN for BizTalk to generate the XML documents in the library, so I figured I’d just fill it out directly.  Same difference right?  Well it turns out when I edit the document directly from WSS, I don’t have the restrictions on my fields.   OK, now I’m doubly confused, but it does give me something to work with.  My first thought was that the direct edit is creating a new document while editing the BizTalk generated documents is editing an existing document.  I tested the theory by inserting all the same fields as the BizTalk document, saving it and then going back to edit it again…

Well, I was able to still edit my document.  So what then is the problem?  I saved both XML files to my local machine and then used my trusty tool for file comparison CompareIt! 3 by Grig Software to spot the difference.  Here’s the BizTalk generated XML document:

 

<?xml version="1.0" encoding="utf-8"?>

<?mso-infoPathSolution solutionVersion="1.0.0.1" productVersion="11.0.6357" PIVersion="1.0.0.0" href="http://home/sites/pas/PASInput/Forms/template.xsn&quot; name="urn:schemas-microsoft-com:office:infopath:PASInput:" language="en-us" ?>

<?mso-application progid="InfoPath.Document"?>

<PAS_Record>

  <EventCode>A08</EventCode>

  <RegNum>1111111111</RegNum>

  <LastName>Doe</LastName>

  <MaidenName></MaidenName>

  <FirstName>John</FirstName>

  <MI></MI>

  <SSN>123456789</SSN>

  <DOB>19700101</DOB>

  <Gender>M</Gender>

  <Race>W</Race>

  <MaritalStatus>M</MaritalStatus>

  <Address>1 My Way</Address>

  <City>Indianapolis</City>

  <State>IN</State>

  <Zip>46254</Zip>

  <Telephone>

    <HomePhone>(317)555-5555</HomePhone>

    <WorkPhone></WorkPhone>

  </Telephone>

</

PAS_Record>

 

And here’s the WSS generated XML document:

 

<?xml version="1.0" encoding="utf-8"?>

<?mso-infoPathSolution solutionVersion="1.0.0.1" productVersion="11.0.6357" PIVersion="1.0.0.0" href="http://home/sites/pas/PASInput/Forms/template.xsn&quot; name="urn:schemas-microsoft-com:office:infopath:PASInput:" language="en-us" ?>

<?mso-application progid="InfoPath.Document"?>

<PAS_Record>

  <EventCode>A08</EventCode>

  <RegNum>1111111111</RegNum>

  <PreRegNumber></PreRegNumber>

  <LastName>Doe</LastName>

  <MaidenName></MaidenName>

  <FirstName>John</FirstName>

  <MI></MI>

  <SSN>123456789</SSN>

  <DOB>19700101</DOB>

  <Gender>M</Gender>

  <PrimaryLanguage></PrimaryLanguage>

  <Race>W</Race>

  <MaritalStatus>M</MaritalStatus>

  <Address>1 My Way</Address>

  <City>Indianapolis</City>

  <State>IN</State>

  <Zip>46254</Zip>

  <Telephone>

    <HomePhone>(317)555-5555</HomePhone>

    <HomePhoneExt></HomePhoneExt>

    <WorkPhone></WorkPhone>

    <WorkPhoneExt></WorkPhoneExt>

  </Telephone>

</PAS_Record>

 

Can you spot the problem?  If not, take a look at this snapshot from CompareIt!.

 

 

As you can see, the WSS version actually included a node for each field while the BizTalk version did not…

The bottom line…

InfoPath will protect all fields in a form that maps to a schema for which the underlying data document does not have a representative node… weird but true!

 

Later
C

 

 
3 Comments

Posted by on July 29, 2005 in Office