Viewnify and Notes 7.0 – 7.0.1 – 7.0.2 – please upgrade to 7.0.3!

First the good news: a new release is on its way. No big changes, but some interesting extra features requested by users and some bug fixes.

But this post is a little warning for all Notes 7.0 to 7.0.2 users out there: Claude Sammut informed me about a bug in the tool: in short, after running Viewnify, opening a view in designer and saving it, the view selection formula can get corrupted: the selection formula changes to the formula of the last column of the view.

At first I thought it was a general DXL problem and I tried to create my own fix, but, to my relief, it’s a bug in the Domino DXL engine that was introduced in 7.0 and fixed in 7.0.3. I did a test yesterday and, indeed, after upgrading to 7.0.3 Viewnification seems like a smooth process once again.

Also, I found this confirmation in the fix list for 7.0.3: SPR# STOI6REJ7E – View selection formula used to get copied over by the column formula on import of a view. Fixed the problem reported by setting a correct flag.

Here’s some explanation on the bug, and here you can download the 7.0.3 upgrade.


  1. Thanks for mentioning this… I saw this last week at a client site and it confused the heck out of me. I wasn’t using Viewnify, just an impromptu script to apply some global changes to all views, but as soon as I would make any additional manual changes, the view would go corrupt. As a stop gap, I put in an agent that they can run against all views if the problem resurfaces, but it’s good to know this is a bug IBM’s already fixed.

  2. Tim,
    The thing is, once the selection formula is corrupted, opening and saving the view won’t help, so your agent probably isn’t going to fix this. It’s better to avoid, if possible.

  3. The agent scans each view, determines contextually what the selection should be, and reimports it with the correct formula, which fixes the problem until the view is modified manually again. So it’s resolving their problem, but makes further design changes tedious because the agent has to be run again any time a view is saved again. Should be sufficient motivation for them to upgrade, since this is their most heavily used application.

  4. Sounds like a hell of a job and a pain in the asterisk! :-) Meanwhile I found confirmation for the fix in the fix list, and updated the article accordingly.

  5. This bug is probably the nastiest I have seen – we lost several days work from databases that had been corrupted ( not using viewnify ) – as Tim mentions above you don’t know that you have a problem until you go to change it again

    I would highly recommend adding code to stop viewnify working on versions 7.02 where it will cause corruption


Submit a Comment

Your email address will not be published. Required fields are marked *

7 + 3 =

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>