Enterprise Custom Field (ECF) with formula - #Error

[James]

I create (via PWA Project 2007) ECFs with formulas.
Then, when I insert these ECFs into the project, they output - #Error.

I've simplified (for troubleshooting) the formula to return values such as
"test" for Text type ECFs and 99 for Number type ECFs.

Yet, I am still getting #Error showing as the value.

Has anybody else seen such symptoms? If yes, how did you fix them?

 

[Jack Dahlgren]

Can you post EXACTLY what you are using for the formula?

-Jack

 

[James]

In PWA :

Name = "1 Test"
Entity = Task
Type = Date
Formula = Date()

 

[Jack Dahlgren]

This is different than what you wrote before where you were talking about
text fields and number fields. I don't have an instance of project server
handy, but that formula should work. Are you entering the Name with the
quotation marks? I do not think you should be.

One possibility is that there are some bugs in synchronizing the custom
fields between the local cache and the project. You might consider deleting
the local cache and restarting.

-Jack Dahlgren

 

[James]

For text types, I've tried with and without double(and single) quotes.
My last response, with Date type, was to show the broad scope of the problem
I'm having with ECFs that have a formula.

 

[James]

I looked at some entirely unrelated ECFs and noticed that one stated "The
formula contains a syntax error or contains a reference to an unrecognized
field or function name".

In its formula the field references were like the following: [MSPJ188776508].
I'm not allowed to change this field right now; but, this is not the
original field value and it looks suspicious to me.

Given that this indicates a problem -
1) Do you know how this sort of a change (by the system) happens, so that I
may prevent it in the future?

2) Is this a behavior of EPM, that a problem in one field's formula can
manifest itself in an entirely unrelated field?

 

[Jack Dahlgren]

Hmmm...
That field reference looks like one of the custom fields. They usually have
numbers in that range but I don't have docs available to look it up right
now. Just as an example, Enterprise Text1 is 188744479. You can get this
value by using the FieldNameToFieldConstant() method.

I think you have some issues with synchronizing between project and project
server. Did you try deleting your cache and restarting project? That is the
first thing I'd do. As for why it happens, there were some bugs in custom
fields in Project 2007. Do you have the latest service pack installed on both
the client and server?

-Jack Dahlgren

I looked at some entirely unrelated ECFs and noticed that one stated "The
formula contains a syntax error or contains a reference to an unrecognized
field or function name".

In its formula the field references were like the following: [MSPJ188776508].
I'm not allowed to change this field right now; but, this is not the
original field value and it looks suspicious to me.

Given that this indicates a problem -
1) Do you know how this sort of a change (by the system) happens, so that I
may prevent it in the future?

2) Is this a behavior of EPM, that a problem in one field's formula can
manifest itself in an entirely unrelated field?

--
Thanks, James

This is different than what you wrote before where you were talking about
text fields and number fields. I don't have an instance of project server
handy, but that formula should work. Are you entering the Name with the
quotation marks? I do not think you should be.

One possibility is that there are some bugs in synchronizing the custom
fields between the local cache and the project. You might consider deleting
the local cache and restarting.

-Jack Dahlgren

 

[James]

To close the loop - I redid the formula on the 'unrelated' suspect ECF and
now all the ECFs with formulas are working fine.

Thank you much for your considerate discussions.
--
Thanks, James

Hmmm...
That field reference looks like one of the custom fields. They usually have
numbers in that range but I don't have docs available to look it up right
now. Just as an example, Enterprise Text1 is 188744479. You can get this
value by using the FieldNameToFieldConstant() method.

I think you have some issues with synchronizing between project and project
server. Did you try deleting your cache and restarting project? That is the
first thing I'd do. As for why it happens, there were some bugs in custom
fields in Project 2007. Do you have the latest service pack installed on both
the client and server?

-Jack Dahlgren

I looked at some entirely unrelated ECFs and noticed that one stated "The
formula contains a syntax error or contains a reference to an unrecognized
field or function name".

In its formula the field references were like the following: [MSPJ188776508].
I'm not allowed to change this field right now; but, this is not the
original field value and it looks suspicious to me.

Given that this indicates a problem -
1) Do you know how this sort of a change (by the system) happens, so that I
may prevent it in the future?

2) Is this a behavior of EPM, that a problem in one field's formula can
manifest itself in an entirely unrelated field?

--
Thanks, James

This is different than what you wrote before where you were talking about
text fields and number fields. I don't have an instance of project server
handy, but that formula should work. Are you entering the Name with the
quotation marks? I do not think you should be.

One possibility is that there are some bugs in synchronizing the custom
fields between the local cache and the project. You might consider deleting
the local cache and restarting.

-Jack Dahlgren


:

In PWA :

Name = "1 Test"
Entity = Task
Type = Date
Formula = Date()

--
Thanks, James


:

Can you post EXACTLY what you are using for the formula?

-Jack

:

I create (via PWA Project 2007) ECFs with formulas.
Then, when I insert these ECFs into the project, they output - #Error.

I've simplified (for troubleshooting) the formula to return values such as
"test" for Text type ECFs and 99 for Number type ECFs.

Yet, I am still getting #Error showing as the value.

Has anybody else seen such symptoms? If yes, how did you fix them?

 

[James]

I was doing some looking around and I found that 201327238 and 205521542 are
also Enterprise Text1 ?!?

In fact, in the range 201326592 to 205521700 there is duplication of the
field constants.

Do you know what's going on here?

--
Thanks, James

Hmmm...
That field reference looks like one of the custom fields. They usually have
numbers in that range but I don't have docs available to look it up right
now. Just as an example, Enterprise Text1 is 188744479. You can get this
value by using the FieldNameToFieldConstant() method.

I think you have some issues with synchronizing between project and project
server. Did you try deleting your cache and restarting project? That is the
first thing I'd do. As for why it happens, there were some bugs in custom
fields in Project 2007. Do you have the latest service pack installed on both
the client and server?

-Jack Dahlgren

I looked at some entirely unrelated ECFs and noticed that one stated "The
formula contains a syntax error or contains a reference to an unrecognized
field or function name".

In its formula the field references were like the following: [MSPJ188776508].
I'm not allowed to change this field right now; but, this is not the
original field value and it looks suspicious to me.

Given that this indicates a problem -
1) Do you know how this sort of a change (by the system) happens, so that I
may prevent it in the future?

2) Is this a behavior of EPM, that a problem in one field's formula can
manifest itself in an entirely unrelated field?

--
Thanks, James

This is different than what you wrote before where you were talking about
text fields and number fields. I don't have an instance of project server
handy, but that formula should work. Are you entering the Name with the
quotation marks? I do not think you should be.

One possibility is that there are some bugs in synchronizing the custom
fields between the local cache and the project. You might consider deleting
the local cache and restarting.

-Jack Dahlgren


:

In PWA :

Name = "1 Test"
Entity = Task
Type = Date
Formula = Date()

--
Thanks, James


:

Can you post EXACTLY what you are using for the formula?

-Jack

:

I create (via PWA Project 2007) ECFs with formulas.
Then, when I insert these ECFs into the project, they output - #Error.

I've simplified (for troubleshooting) the formula to return values such as
"test" for Text type ECFs and 99 for Number type ECFs.

Yet, I am still getting #Error showing as the value.

Has anybody else seen such symptoms? If yes, how did you fix them?

 

[Jack Dahlgren]

Yes, You have to look at the type. There are resource, assignment and task
Enterprise Text1 fields.

-Jack Dahlgren

I was doing some looking around and I found that 201327238 and 205521542
are
also Enterprise Text1 ?!?

In fact, in the range 201326592 to 205521700 there is duplication of the
field constants.

Do you know what's going on here?

--
Thanks, James

Hmmm...
That field reference looks like one of the custom fields. They usually
have
numbers in that range but I don't have docs available to look it up right
now. Just as an example, Enterprise Text1 is 188744479. You can get this
value by using the FieldNameToFieldConstant() method.

I think you have some issues with synchronizing between project and
project
server. Did you try deleting your cache and restarting project? That is
the
first thing I'd do. As for why it happens, there were some bugs in custom
fields in Project 2007. Do you have the latest service pack installed on
both
the client and server?

-Jack Dahlgren

I looked at some entirely unrelated ECFs and noticed that one stated
"The
formula contains a syntax error or contains a reference to an
unrecognized
field or function name".

In its formula the field references were like the following:
[MSPJ188776508].
I'm not allowed to change this field right now; but, this is not the
original field value and it looks suspicious to me.

Given that this indicates a problem -
1) Do you know how this sort of a change (by the system) happens, so
that I
may prevent it in the future?

2) Is this a behavior of EPM, that a problem in one field's formula can
manifest itself in an entirely unrelated field?

--
Thanks, James


:

This is different than what you wrote before where you were talking
about
text fields and number fields. I don't have an instance of project
server
handy, but that formula should work. Are you entering the Name with
the
quotation marks? I do not think you should be.

One possibility is that there are some bugs in synchronizing the
custom
fields between the local cache and the project. You might consider
deleting
the local cache and restarting.

-Jack Dahlgren


:

In PWA :

Name = "1 Test"
Entity = Task
Type = Date
Formula = Date()

--
Thanks, James


:

Can you post EXACTLY what you are using for the formula?

-Jack

:

I create (via PWA Project 2007) ECFs with formulas.
Then, when I insert these ECFs into the project, they output -
#Error.

I've simplified (for troubleshooting) the formula to return
values such as
"test" for Text type ECFs and 99 for Number type ECFs.

Yet, I am still getting #Error showing as the value.

Has anybody else seen such symptoms? If yes, how did you fix
them?

 

[James]

Jack,

I encounter the following problems :

1) The FieldNameToFieldConstant method's 2nd parameter (PjFieldType)
has values : pjTask, pjResource or pjProject (no pjAssignment)

2) The pjTask and pjProject return the same ID

3) The 3rd constant is not returned

Here is a printout of the the "Enterprise Text1" condition.

ECF ambiguity
=============

Using the FieldConstantToFieldName method

ID = 188744479 --> Enterprise Text1
ID = 201327238 --> Enterprise Text1
ID = 205521542 --> Enterprise Text1

Using the FieldNameToFieldConstant method

Enterprise Text1 (pjProject) -->188744479
Enterprise Text1 (pjTask) -->188744479
Enterprise Text1 (pjResource) -->205521542

As you can see the ID = 201327238 is not returned by any of these calls;
and ID = 188744479 is returned by both pjProject and pjTask.

Can you explain?

--
Thanks, James

Yes, You have to look at the type. There are resource, assignment and task
Enterprise Text1 fields.

-Jack Dahlgren

I was doing some looking around and I found that 201327238 and 205521542
are
also Enterprise Text1 ?!?

In fact, in the range 201326592 to 205521700 there is duplication of the
field constants.

Do you know what's going on here?

--
Thanks, James

Hmmm...
That field reference looks like one of the custom fields. They usually
have
numbers in that range but I don't have docs available to look it up right
now. Just as an example, Enterprise Text1 is 188744479. You can get this
value by using the FieldNameToFieldConstant() method.

I think you have some issues with synchronizing between project and
project
server. Did you try deleting your cache and restarting project? That is
the
first thing I'd do. As for why it happens, there were some bugs in custom
fields in Project 2007. Do you have the latest service pack installed on
both
the client and server?

-Jack Dahlgren


:

I looked at some entirely unrelated ECFs and noticed that one stated
"The
formula contains a syntax error or contains a reference to an
unrecognized
field or function name".

In its formula the field references were like the following:
[MSPJ188776508].
I'm not allowed to change this field right now; but, this is not the
original field value and it looks suspicious to me.

Given that this indicates a problem -
1) Do you know how this sort of a change (by the system) happens, so
that I
may prevent it in the future?

2) Is this a behavior of EPM, that a problem in one field's formula can
manifest itself in an entirely unrelated field?

--
Thanks, James


:

This is different than what you wrote before where you were talking
about
text fields and number fields. I don't have an instance of project
server
handy, but that formula should work. Are you entering the Name with
the
quotation marks? I do not think you should be.

One possibility is that there are some bugs in synchronizing the
custom
fields between the local cache and the project. You might consider
deleting
the local cache and restarting.

-Jack Dahlgren


:

In PWA :

Name = "1 Test"
Entity = Task
Type = Date
Formula = Date()

--
Thanks, James


:

Can you post EXACTLY what you are using for the formula?

-Jack

:

I create (via PWA Project 2007) ECFs with formulas.
Then, when I insert these ECFs into the project, they output -
#Error.

I've simplified (for troubleshooting) the formula to return
values such as
"test" for Text type ECFs and 99 for Number type ECFs.

Yet, I am still getting #Error showing as the value.

Has anybody else seen such symptoms? If yes, how did you fix
them?