Filtering SharePoint List by SharePoint Group and Status

In order to display only not closed (Abgeschlossen) items assigned to the group that one is a member of, I added the following where clause to the form query, where "Gruppe" is the group that one is a member of and "Status" is the state for all not closed items.

Where><
    And><
        Neq><FieldRef Name="Status"/><Value Type="Text">Abgeschlossen</Value></Neq><
        Or><
            Membership Type="CurrentUserGroups"><FieldRef Name="Gruppe"/></Membership><
            Eq><
                FieldRef Name="Gruppe"/><Value Type="Integer"><UserID Type="Integer"/></Value><
            /Eq><

        /Or><
    /And><
/Where><

Advertisements

Changing SharePoint’s HelpDesk Service Request Status

Just in case that I forget, in order to change the service request status, one has to modify or add a SRStatus_Choice in:

%programfiles%Common FilesMicrosoft SharedWeb Server Extensions12Resourceshlpdsk.resx

In this example, I renamed existing ones and added two more:

  <data name="SRStatus_Choice1" xml:space="preserve">
    <value>Nicht Begonnen</value>
  </data>
  <data name="SRStatus_Choice2" xml:space="preserve">
    <value>Warteschlange</value>
  </data>
  <data name="SRStatus_Choice3" xml:space="preserve">
    <value>In Bearbeitung</value>
  </data>
  <data name="SRStatus_Choice4" xml:space="preserve">
    <value>Abgeschlossen</value>
  </data>
  <data name="SRStatus_Choice5" xml:space="preserve">
    <value>Zurückgestellt</value>
  </data>
  <data name="SRStatus_Choice6" xml:space="preserve">
    <value>Wartet auf jemand anderen</value>
  </data>

For additions need to be appended in this schema:

%programfiles%Common FilesMicrosoft SharedWeb Server Extensions12TEMPLATEFEATURESHelpDeskServiceRequestsListservicerequestschema.xml

In this example, I added choices 4 and 5:

            <Default>$Resources:hlpdsk,SRStatus_Choice1;</Default>
            <CHOICES>
              <CHOICE>$Resources:hlpdsk,SRStatus_Choice1;</CHOICE>
              <CHOICE>$Resources:hlpdsk,SRStatus_Choice2;</CHOICE>
              <CHOICE>$Resources:hlpdsk,SRStatus_Choice3;</CHOICE>
              <CHOICE>$Resources:hlpdsk,SRStatus_Choice4;</CHOICE>
              <CHOICE>$Resources:hlpdsk,SRStatus_Choice5;</CHOICE>
              <CHOICE>$Resources:hlpdsk,SRStatus_Choice6;</CHOICE>
            </CHOICES>

After making the changes, restart the IIS.

Session log on for Microsoft Dynamics failed. Dynamics Adapter Logon failed.

After starting the Dynamics AX 2009 Synchronization Service, the Project Server Integration components wouldn’t install and the following error got written twice each second into the server application log:

Session log on for Microsoft Dynamics failed.

Dynamics Adapter Logon failed.

Microsoft.Dynamics.Framework.BusinessConnector.Session.Exceptions.NonFatalSessionException
   at Microsoft.Dynamics.Framework.BusinessConnector.Session.DynamicsSession.HandleException(String message, Exception exception, HandleExceptionCallback callback)
   at Microsoft.Dynamics.Framework.BusinessConnector.Session.DynamicsAdapter.Logon(String company, String language, String objectServer, String configuration)
   at Microsoft.Dynamics.SyncServices.SyncAxSession.OnLogon(IAxaptaAdapter axaptaAdapter)
   at Microsoft.Dynamics.Framework.BusinessConnector.Session.DynamicsSession.Init(ICacheContext context)

Microsoft.Dynamics.BusinessConnectorNet.NoSecurityKeyException
   at Microsoft.Dynamics.BusinessConnectorNet.Axapta.Logon(BC_PROXY_ACCOUNT_INFO* pBCProxyAccountInfo, String company, String language, String objectServer, String configuration)
   at Microsoft.Dynamics.BusinessConnectorNet.Axapta.Logon(String company, String language, String objectServer, String configuration)
   at Microsoft.Dynamics.Framework.BusinessConnector.Session.DynamicsAdapter.Logon(String company, String language, String objectServer, String configuration)

The workaround is to assign the Admin group to the Synchronization Service Account in Dynamics under Administration/Administration Area/Users.  Being a member of the SyncAdmin group alone didn’t seem to do the trick. Afterwards, restart the Dynamics AX 2009 Synchronization Service.