How to clear field in sharepoint workflow!

Unfortunately there is no explicit function to clear a field within a workflow, but there is a workaround. It works similiar to the [Me] and [Today] trick.

1. Create a column. It does not matter how you name it or which type it is.
2. In your workflow use "Set Field in Current Item" like "Set to .
3. Save your workflow.
4. Delete the new column.

Thanks to Nammy. :-)

Kommentare

Beliebte Posts aus diesem Blog

Error: HPDMG0764E An internal error has occurred. (status 0x14c012fc)

Error: HPDMG0764E An internal error has occurred. (status 0x14c012fc) pdadmin sec_master> user create dg1234 uid=dg1234,cn=team1,cn=users,o=company lala lala ********** Could not perform the administration request Error: HPDMG0764E An internal error has occurred. (status 0x14c012fc) Description: After the upgrade from Policy Director (policy server) V5.1 to V6.0 the errors above occured when trying to write to the registry. Solution: The task of updating the ldap schema did not work well for some reason. After doing it again the errors did not occur again: # ivrgy_tool -d -h ldap_host -p port -D ldap_admin -w pwd schema

mRemoteNG does not start (crashs) - all of a sudden

All of a sudden my mRemoteNG did not start anymore. It seemed to start, but did not come up and vanished. Thanks to http://forum.mremoteng.org/viewtopic.php?f=3&t=2989 I realised that I had to force a shutdown earlier. Solution: Remove - %APPDATA%\mRemoteNG - %USERPROFILE%\AppData\Local\mRemoteNG

WebSphere Application Server LDAP: The administrative user ID does not exist in the user repository.

When you try to enable global security with ldap authentication you get the following error when configuring your ldap repository (IBM Directory Server): The administrative user ID does not exist in the user repository. Reason: The bind user must be searchable. This means that an ldapsearch with this user as bind user must return his own entry. If this does not work, you have to add an aclEntry: vi change-was7101-aclentry.ldif dn: uid=was7101,cn=mygroup,cn=admusr,o=mycomp aclentry: access-id:UID=WAS7101,CN=MYGROUP,CN=ADMUSR,O=MYCOMP:normal:rsc $ ldapmodify -h myhost -x -D "cn=root" -w ******* -f change-was7101-aclentry.ldif modifying entry "uid=was7101,cn=mygroup,cn=admusr,o=mycomp" Now user was7101 can do an ldapsearch to find itself and therefore you can use it to configure you LDAP repository. This article gave me the hint: http://www-01.ibm.com/support/docview.wss?rs=767&uid=swg21219253

Dani's Middleware

Dieses Blog durchsuchen