Notes视图Web访问属性未纳入源代码控制问题咨询

I've run into this exact issue with Domino R10/R11 ODP exports before—those advanced view properties like Allow Domino Data Services and Allow Web Crawler Indexing don't get captured in the default On Disk Project export, even with "Use Binary DXL" disabled. Here are the reliable workarounds to fix this:

1. Manually Update the View's XML File in ODP #

The simplest immediate fix is to edit the view's .view.xml file directly in your Git repo:

• Navigate to your ODP's views folder and open the XML file for the affected view.
• Add the missing attributes to the root <view> tag:
  • For Domino Data Services: allowdataservices="true"
  • For Web Crawler Indexing: allowindexing="true"
• Example modified snippet:

  <view name="YourViewName" allowdataservices="true" allowindexing="true" ...>
    <!-- Existing view configuration -->
  </view>
  

Commit this change, and next time you deploy the ODP, these settings will apply to the production NSF.

2. Force Full DXL Export in Domino Designer #

Domino Designer has a hidden preference to export all design element properties instead of a trimmed subset. To enable it:

• Close Domino Designer completely.
• Locate the plugin_customization.ini file in your Designer installation directory (usually C:\Program Files\HCL\Domino Designer\ on Windows).
• Add this line to the file:

  com.ibm.designer.domino.ide.resources/export.full.dxl=true
  

• Restart Designer, then re-export your NSF to ODP (or let source control sync the changes). This will ensure all advanced view properties are included in the XML files going forward.

3. Scripted DXL Export/Import (For Batch Scenarios) #

If you have multiple views to manage, a scripted approach ensures consistent capture of all properties:

• Write a LotusScript or Java agent to export the full DXL of your views. Here's a quick LotusScript example:

  Sub Initialize
      Dim session As New NotesSession
      Dim db As NotesDatabase
      Dim view As NotesView
      Dim stream As NotesStream
      Dim filePath As String
      
      Set db = session.CurrentDatabase
      Set view = db.GetView("YourViewName")
      Set stream = session.CreateStream()
      
      ' Save DXL to your ODP's views directory
      filePath = "C:\YourRepoPath\odp\views\YourViewName.dxl"
      If stream.Open(filePath) Then
          stream.WriteText(view.ExportDXL())
          stream.Close()
      End If
  End Sub
  

• Add these DXL files to your Git repo, and use a similar script to import them during deployment. This avoids relying on Designer's ODP export limitations entirely.

Note that this is a known limitation in R10/R11—HCL addressed some of these ODP gaps in later releases like R12, but for older versions, the above methods are your best bets.

内容的提问来源于stack exchange，提问作者Rob Mason