Skip Ribbon Commands
Skip to main content

Knowledge Base

:

Top Link Bar

Quick Launch
Home
October 25
Customizing the New button options in a list
by  Brandon BakerNo presence information  on 10/25/2010 12:33 PM

In any WorkEngine list, you have the option to change the drop down menu text and the create/Ok button associated with the creation of the list item.  See example below.
The following example uses the WorkEngine Project Center list.

In the Project Center list, when creating a new item, by default the name of the item option is Project in the drop down, the name of the form is New Project, and the name of the button to create the new item is Create Project. See screenshots below.




To change the the text value in the drop down and the create button, follow the instructions below.

1. Navigate to Site Actions -> Site Settings -> Site libraries and lists.
2. Double-click the hyperlink of the list for which you want to make the change to.
3. Select General Settings  and scroll down to the New Item Settings.
4. Enter your new name and click the Save button.


5. Navigate back to the list and you will find your changes are represented in the list item and the create button. 

 

 

 

Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
October 25
Error:The method is not available in this situation
by  Brandon BakerNo presence information  on 10/25/2010 12:24 PM

Symptoms
You receive the following error when publishing from Microsoft Project to WorkEngine:

Error:The method is not available in this situation.
Cause
Sometimes when the cursor is focused inside a cell the Microsoft Project menu buttons are disabled and to enable them you must click elsewhere.  This is a Microsoft Project behavior and this error will occur when a project is published using Project Publisher while the menus are disabled.
Workaround/Resolution
Move the focus of the cursor around until the Microsoft Project menus are no longer disabled, then try publishing again.
​

Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
October 25
Error: Item has already been added
by  Brandon BakerNo presence information  on 10/25/2010 12:21 PM

 

Symptoms
You receive the following error when attempting to update your Microsoft Project schedule using Project Publisher:

Error:  Item has already been added.  Key in dictionary: '<somenumber>' Key being added:  '<somenumber>'
Cause
This error is caused by the Resource Names field in the WorkEngine Task Center List being configured as "editable".
Workaround/Resolution
The Resource Names field in the Task Center List of WorkEngine cannot be configured as "editable".

1.  From the Task Center List, select List Settings within the Settings menu.
2.  Select the "Manage Editable Fields" link under General Settings.
3.  Ensure that the "Show In New Form" and "Show In Edit Form" checkboxes are unchecked.
4.  Click the OK button when finished.
​

 

Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
October 25
Publisher key has exceeded the maximum number of activations
by  Brandon BakerNo presence information  on 10/25/2010 12:05 PM

 

Symptoms
After entering the Project Publisher activation key during the install process, message appears stating the key has exceeded the number of activations allowed.
Cause
Cause 1: An extra space is being copied to the beginning and/or end of the company name and/or activation key.

Cause 2: When activating user does not enter in activation information correctly.
Workaround/Resolution
Resolution 1: Ensure that there are no extra spaces at the beginning and/or end of the company name and/or activation key.  DO Not Copy and Paste the Activation Key or Company Name.

Resolution 2: Please enter the activation information exactly as received in purchase email to include capitalization and punctuation of the characters in both the company name and the activation key.
Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
October 22
Error Message: Object Moved
by  Brandon BakerNo presence information  on 10/22/2010 12:32 PM

 

Symptoms

When publishing a Microsoft project schedule the following error message appears: 
Object moved
Object moved to
https://portal.id.ethz.ch/projekte/lb-audit/_layouts/1033/error.aspx
ErrorText=The file vti_bin/lists.asmx does not exist here.

 

Cause
Either the server URL is incorrect and/or web services is not turned on. Here are some steps to ensure that web services is turned on and the correct URL is being used.

 

Workaround/Resolution
1. Navigate to Central Administration for SharePoint
2. Under the "Application Management" tab you will find an area called "Application Security"
3. Click "User Permissions for Web Application"
4. Ensure that the option for "Use Remote Interfaces" is checked
5. Ensure that the correct URL is being used when you are publishing to your SharePoint site.

**Note**
Project Publisher behaves differently when Microsoft Project is connected to Project Server because WorkEngine integrates with Project Server. If you're not using the version of WorkEngine that integrates with Project Server and you attempt to publish while connected to Project Server, this error may occur. Please try logging into Microsoft Project with the "Computer" profile and then publishing.
Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
October 22
HTML <div> Tags Appear in SharePoint Fields
by  Brandon BakerNo presence information  on 10/22/2010 12:27 PM

 

Symptoms
<div> tags appear in SharePoint fields after publishing from Microsoft Project using Project Publisher.
Cause
The related fields in SharePoint are set to rich text.
Workaround/Resolution
Change the corresponding fields in SharePoint to 'plain text'
Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
October 22
Project Publisher User Guide
by  Brandon BakerNo presence information  on 10/22/2010 12:18 PM

Please click here to download the Project Publisher user guide.

 

 

 

 

 

Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
October 22
Publishing Error Message: Disabled Publishing
by  Brandon BakerNo presence information  on 10/22/2010 12:03 PM

Symptoms
You receive the following error message when attempting to publish .MPP files to a SharePoint site:

Cause
The publishing feature has been disabled on the site for which you are attempting to publish to.  By default, the 'Disable Publishing' setting is disabled for top level site collection templates.  WorkEngine does not recommend, or support, publishing to the site collection template. 
Workaround/Resolution
Below are instructions to enable publishing to a top level site collection:
1. Select Site Actions from the site homepage, and then click on Site Settings in the drop down list
2. Click on Web Settings located in the "EPM Live Administration" column
3. Uncheck the Disable Publishing check box
​

Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
October 22
Creating Filtered Lookups Fields in a SharePoint 2007
by  Brandon BakerNo presence information  on 10/22/2010 11:58 AM

 

SharePoint does not support this OOTB (out of the box), however this can be accomplished using SharePoint Designer.

        Create a new Custom Form
  • Open SharePoint Designer, open the NewForm.aspx page, and create a new aspx page from the NewForm.aspx and save it as NewFormFiltered.aspx
  • Delete the list Web part which exists and Click Insert > SharePoint Controls > Custom List Form, and choose based on a New Item (since you are editing the New Item form).

 



        Create a new DataSource to the List you need to filter upon
  • In the custom page you are creating find the DataSource tag in the source code sharepoint:spdatasource and create another datasource similar to the one which exists, however with a new different datasource ID e.g. FilteredDS, and a different SelectCommand.
  • The SelectCommand is used to create a query which filters your data e.g. if you filter on the Open Status it should contain something similar to the following:
  • This filter can be written in the Tag Properties of the DataSource.
  • Any parameters contained within the datasource and which contain List GUIDs based on the list you are editing should be edited to point to the GUID of the list you are filtering on.
        Add a SharePoint DropDown List
  • Find the lookup field which you want to filter in the page, and comment out the SharePoint:FormField. Insert a SharePoint:DVDropDownList and customize the properties similar to the following:

Where ff9 should be the position in the FormField you have commented out, the datasourceid should be the id of the datasource you created, and the @Vacancy should be the name of your colum.

 

Save and test by clicking on New Item in the customised list, and in the address change the address of the page which comes up to the name of the page you have customised. If you’ve done everything correctly, you should have a drop down list bound to the filtered data source you created.
 

 

        Edit the List such that New button refers to the new page you have created
  • Once you’ve ensured that the List is ok, you need to edit the List Properties such that your edited page is displayed when you press the New Item button.
  • Go to the List Properties, Click on the Support Files tab and choose your page as the NewItemForm. Make sure the Content Item is set to Item or Task or your content Item not Folder. If it is set to Folder your changes are silently ignored, simply not saved.
 

 



The most toublesome parts are getting your data source(s) to filter correctly, and getting the DV drop down list to actually post the data to the list, but with a little playing around you should be able to do it.
 

 

Errors you may encounter: Strangely SharePoint sometimes changes the ID of the datasource to the name plus 0 e.g. FilteredDS0. Since your datasource is still bound to the original name, when you access the page you get an error: "An unexpected error has occurred".

 

Data Source Creations hints: to create your data source, go to the Data Source Library, click on Copy and Modify, create a new data source with the filter you require, same it as XML. Open the XML file and copy the SharePoint datasource from the xml file and paste it into your designer code. Strangely, the Guids in the data source from the XML file do not contain the curly brackets {}, and will result in the drop downs not getting populated until you surround each Guid with curly brackets.
 
Update:
 
BEWARE: Using this method you will be tying yourself down to a list Guid. Thus if you try to export and import onto a different server, you will get an error when you try to load the page since the list (Guid) will not be found. You would have to use designer (again) to update your Guids on the live server! Keep this in mind when using this hack.
 
Update 2:
This solves the problem: Solving the List Guid Export Problem

Update 3: Programmatic solution to filtered lookups - Cascading dropdowns

 

​

 

Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
October 22
Configuring Various Task Statusing Methods Within WorkEngine
by  Brandon BakerNo presence information  on 10/22/2010 10:59 AM

WorkEngine is very flexible in regards to task statusing and that is why it's so important to understand your options.  Here are the supported task statusing methods:

Status Field
This method uses the "Status" field to drive % Complete.  Task assignees can update their "Status" using a dropdown list in SharePoint and % Complete will automatically be updated.  For example, if the Status field is set to "Completed", the system will automatically updated % Complete to 100.  This method is best suited for very simple "checklist" type statusing.

Note:  Only the "Completed" status value will drive % Complete.

% Complete
This method simply allows the assignee to update the task % Complete field.

Remaining Work
This method simply allows the assignee to update the task Remaining Work field.

Actual Work
This method simply allows the assignee to update the task Actual Work field.

Actual Work & Remaining Work
This method simply allows the assignee to update the task Actual Work and Remaining Work fields.

Once a task statusing method is selected, it's important to make sure that the Task List edit screen is configured correctly so that users are directed to update the correct fields.  Here is how you set which Task fields are editable:

1.  Choose List Settings from the Settings menu of the Task Center List.
2.  Under General Settings, select the Manage Editable Fields link.
3.  Deselect the Show In Edit Form column value for the columns that you want to remove from the edit screen.  For example, if you choose to status using the % Complete method, you need to make sure that Remaining Work and Actual Work are not "shown in edit form".

NOTE:  In order for information to be imported back into Microsoft Project, the field must be "shown in edit form".

----------------------------------------------------------------------------------------------------------------------

Here are some additional notes in regards to statusing.  For both Task Based and Assignment Based publishing, the following statements are true:

- Actual Start will only be updated in Microsoft Project if % Complete > 0.  You can't say that you've started the task and the Percent Complete is still 0.
- Actual Finish will only be updated in Microsoft Project if % Complete = 100.   You can't say that you've finished the task if the Percent Complete is not 100.
- Specifying the Finish date in SharePoint and then importing this into Microsoft Project will result in a "Finish No Earlier Than" contraint on the task.

If you are using Assignment Based publishing, you will experience some different behavior at the task level, although the Task Usage view (assignment level) behavior will remain the same.

- The task level Actual Finish will only be updated in Microsoft Project if all assignment level assignments have Actual Finish values specified.  If you view the Task Usage view in Microsoft Project, you will see the assignment level values.  When publishing using Assignment Based, it's important to remember that values such as Actual Finish may be updated for the assignment in the Task Usage view but the task level values may be different depending on the number of assignments etc...
​

Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
1 - 10Next
Alert Me Alert Me