|
|
Search
You searched for the word(s):
Showing page 1 of 2 (11 total posts)
< 1 second(s)
-
I think I've solved this.
First, the SQL Statement had to explicitly list the column names: "Select * from ..." was not sufficient.
Secondly, the column names must be specified without the brackets and using an underscore for the space. Thus the column [Current Phase] in the SQL statement had to be specified in the Column to ...
-
I'm using the Execute SQL action and the Specify Column Names option and I get nothing returned. I've confirmed that the query itself works by having the result go to a collection, but when I specify the columns, I get nothing returned.
My column names are [ProjectName], [Current Phase], and [PHDate]. I've specified them with and ...
-
What ever happened to this need (the ability to modify the command timeout)?
Thank you.
-
we've subsequently restored the production NW database to the test environment and attached it to that instance, but are still seeing the same result.
Are we going to have to delete the UDA's from the database?
-
We have SharePoint 2010 with Project Server 2010. We migrated the Project Server Databases and the Content database for Project Server to our TEST environment, but we didn't migrate the NW Database.
We may have problems copying the NW database from PROD to TEST because it impacts a much broader set of users (beyond Project Server's Site ...
-
We recently restored from our Production environment to a Test environment. The Manage User Defined Actions page shows no items, however, when I attempt to import a UDA, it states that a UDA with that name already exists.
Workflows that use the UDAs execute, but when I attempt to edit the workflows, the UDAs already in the workflow indicate that ...
-
We've created several UDAs at the site parent but when attempting to create workflows in child sites, the UDAs are not available. Is there a synchronization step to make those available, or do I have to move them there manually?
(If I have to move them there manually, then it kind of defeats the purpose of a UDA - defining it in one ...
-
Interestingly, I found that if I replaced the quote with a space instead of null, I did not have the problem:
fn-Replace({TextStart}{WorkflowVariable:txtProjectName}{TextEnd},{TextStart}"{TextEnd},{TextStart} {TextEnd})
I did have some issues with double spaces, but that just took one more replace.
-
I am trying to use the fn-Replace function to remove the double-quote from a field. However, the result is that all the text is removed. I am using the following statement:
fn-Replace({TextStart}{WorkflowVariable:txtProjectName}{TextEnd},{TextStart}"{TextEnd},{TextStart}{TextEnd})
{WorkflowVariable:txtProjectName} is a text variable that ...
-
I had a similar issue working to replace a large number of individual characters. Instead of writing one long set of fn-Replace entries, I created a sharepoint list with an entry for each character I wanted to replace. Then I use a collection object to walk through each character and perform individual replace functions for each occurance of the ...
1
|
|
|