MS Project task-level calculated custom field displaying incorrect value - ms-project

I have a custom field defined on a task level that is calculated using the value of another task-level custom field.
The value of the calculated field, "Completed" is either 1 or 0, based on the value of the other field "Completed Date." If Completed Date has a value, Completed = 1, else Completed = 0. Completed Date is a Date type field.
I am currently having a problem where in a handful of cases, Completed is 1 when Completed Date has no value.
The formula for Completed is
IIf(IsDate([Completed Date]) = True, 1, 0)
99% of the values calculate correctly, but the 1% is causing problems. The only way to correct the value of Completed is to put a value in Completed Date and then remove the value from Completed Date.
Has anyone else experienced Project calculated fields calculating incorrectly like this? Are there any fixes?

The solution that worked for me, provided by Ismet Kocaman over at the MSDN forums, was:
Do not use IsDate for NA check. Instead, use iif( [Completed Date] = ProjDateValue("NA"), 0, 1 )

Related

Custom field days remaining to finish a task

How can I create a formula that allows me, in a custom field, to calculate the remaining days of the task, with respect to the last data cutoff (Status Date), as long as it is not 100% complete?
I have tried to create a simple formula to perform the initial test of the remaining days, using the status date field and the end field, [End]-[Status Date], but the result is wrong.
Just use the "Remaining Duration" column that already exists in MS Project, it shows exactly what you are asking for.

count distinct of text field in data studio increased when using filter

I want to count the number of sessions with a certain event label in google data studio. I have created a new field in data studio on a google analytics source like this:
COUNT_DISTINCT(CASE WHEN Event Label = "Form Start" THEN Session ID ELSE "" END)
where Session ID is a custom dimension from GA (string).
The problem is that when I for example pull this new metric to a scorecard, I get a value of 6, if I then add a filter on this scorecard with Event Label = "Form Start" (the exact same event label as in the case statement of the new field) the metric is increased to 23! (which is the correct number).
Is there some data truncation going on in data studio behind the scenes or why does using the filter increase the distinct count?
The weird numbers you're seeing could be due to sampling. At the bottom of the report in "view" mode, it should indicate if the numbers are sampled or not.
Also, the Unique Events metric should tell you the number of times a specific event happened per session. You might not need to do all that custom work in data studio, just a filter for the label.
I might be missing something that requires the COUNT_DISTINCT function, but would a simpler, different formula work?
CASE
WHEN Event Label = "Form Start" THEN 1
ELSE 0
END
This would create a number field that that can be used in the metric element of a Scorecard with multiple aggregation options? The key option being SUM :)
I had a similar problem I think, where I was trying to tally all the pages with a certain category in the meta:
CASE
WHEN REGEXP_MATCH(idio:industry, '.*Agriculture.*') THEN "Agriculture"
else "Others"
END
In your case, I think you would use this:
CASE
WHEN REGEXP_MATCH(Event Label, '.*Form Start.*') THEN Session ID
else "Others"
END

Goal conversion not registering when using event value condition equals 0

I am tracking events with category of "Outbound" and value set to either 0 or positive integer. I am using the same code to track the event, regardless of the value, and have confirmed that when the value is set to 0, that is what the GA code is submitting, and that the value is not null.
When defining an Event type goal with Value "Greater than" 0, the goals are being properly measured. When defining an Event type goal with Value "Equals to" 0, no goals are being counted, both with the Verify command, real-time conversion data and after several days of confirmed events with Category of "Outbound" and Value of 0 (not null) that should meet this criteria.
Below is a link to a screenshot of the goal details. Can anyone shed some light on why this might be happening?
Goal Definition with Value Condition of Equals to 0
Not sure you are using Google Tag Manager. Are you ?
Eventually try 'label = {{Click URL}}' and leave value blank
The event should specify what the 'Click URL' conditions are (in your case -> greater than 0). But what do you want to measure ? If it's outbound link clicks, specify 'Click URL' does not contain 'your_site.com'

Conditional field value in Access 2007

I created a database to keep track of customer service related follow-ups in a call centre environment.
My table has, among the others, a Date created field, a Due date field and a Status field (Open, Due or Overdue).
I would like the value indicated in the Status field to update automatically as time elapses.
Can this be achieved and how?
This is absolutely possible. Why not? I would suggest you do the following:
(1) add another status to the status field called 'closed'
(2) determine from a logorithmic perspective what 'Due' means (e.g. if the current date falls within 5 days of your due date
(3) Write a query which updates your status either 'due' or 'overdue' depending on what the current date is
UPDATE tblDue SET tblDue.Status = "Due"
WHERE (((tblDue.DueDate)=Now()));
UPDATE tblDue SET tblDue.Status = "Overdue"
WHERE (((tblDue.DueDate)>Now()));

How to put a countdown in a table using asp.net code?

Let's say I have a table called adverts with the following fields: advert_id, name,date_created description, duration, status, user_id, cat_id.
Let's say a user puts a duration of 1 week in the duration field and its status is set to active. After a week has passed, the status is set to inactive in the table.
Can anyone tell me if it's possible to do this with asp.net 4.0 code using visual basic in visual studio 2010 with web forms?
I don't see a reason to update a status at all. Instead of (or in addition to) duration, store the datetime the status is to be set to active (current datetime plus duration). The application can then consider values less than the current datetime as active without having to actually update the row.
If desired, you can still derive the active status as a column the query or as a derived column in the table. For example:
SELECT CASE WHEN active_date <= GETDATE() THEN 'Y' ELSE 'N' END AS active
FROM dbo.adverts;

Resources