Community
Showing results for 
Search instead for 
Do you mean 
Reply

Search "Today" in date field not working in Act! Premium Version 19.1.63.0

Highlighted
Administrator
Posts: 4,041
Country: United_Kingdom

Re: Search "Today" in date field not working in Act! Premium Version 19.1.63.0

[ Edited ]

Hi all,

 

The defect is currently still open. The recent v19.1 update did not include a fix for this issue.

 

@gontranharvey Can you confirm whether looking up 'Today' on custom date/time fields works correctly?

Highlighted
Copper Super Contributor
Posts: 34
Country: Canada

Re: Search "Today" in date field not working in Act! Premium Version 19.1.63.0

it's not logic, but I check and today dont work.
Highlighted
Copper Contributor
Posts: 91
Country: USA

Re: Search "Today" in date field not working in Act! Premium Version 19.1.63.0

[ Edited ]

@Gary W wrote:

Hi all,

 

The defect is currently still open. The recent v19.1 update did not include a fix for this issue.

 

@gontranharvey Can you confirm whether looking up 'Today' on custom date/time fields works correctly?


It appears this defect is still open...

After updating to Act! Premium Version 19.2.146.0, the defect "Today" search on custom date fields continues not to work. 

snap1772.jpg

An Act! user since ACT! for DOS v1.0 (1988)
Highlighted
Administrator
Posts: 4,041
Country: United_Kingdom

Re: Search "Today" in date field not working in Act! Premium Version 19.1.63.0

Hi ptrombetta,

Yes, unfortunately a fix for this defect has not yet been published.
Please can you let us know if you are able to look up 'Today' on custom date/time fields?
Highlighted
Copper Contributor
Posts: 91
Country: USA

Re: Search "Today" in date field not working in Act! Premium Version 19.1.63.0

Yes, a "Today" lookup in a custom date/time field works fine.

We eagerly await the fix of "Today" search on custom date fields as this defect affects and renders the majority of our Smart Tasks inoperative and useless.
An Act! user since ACT! for DOS v1.0 (1988)
Highlighted
Administrator
Posts: 4,041
Country: United_Kingdom

Re: Search "Today" in date field not working in Act! Premium Version 19.1.63.0

Thanks for letting us know. I don't currently have a timeframe for a fix on this issue, so I would suggest swapping the date fields used by your Smart Tasks for date/time fields to work around this current limitation.
Highlighted
Copper Super Contributor
Posts: 34
Country: Canada

Re: Search "Today" in date field not working in Act! Premium Version 19.1.63.0

Same as @ptrombetta.

It's a very bad bug and should not append.

It limits me of a lot of automatization I want to do.

Some days I want to give up on ACT!, there's always a key feature that do not work as it should... like the smartask!!

 

Thanks anyway and hope you fix that as soon as possible.

Highlighted
Administrator
Posts: 4,041
Country: United_Kingdom

Re: Search "Today" in date field not working in Act! Premium Version 19.1.63.0

Thanks both for your continued feedback on this issue. I've placed a note on the defect to highlight the requests from this thread, which will be be reviewed by the Product Management team.
Highlighted
Copper Contributor
Posts: 91
Country: USA

Re: Search "Today" in date field not working in Act! Premium Version 19.1.63.0

[ Edited ]

This issue continues to be unresolved in Act! Premium Version 19.2.146.0, Update 3. We continue to wait for this fix of "Today" search on custom date fields. This defect affects and renders the majority of our Smart Tasks inoperative and useless.

 

Has this defect been reviewed by the Product Management team? What was the outcome?

 

Can you confirm this defect is currently being addressed and a fix is in the works?

 

Thank you.

An Act! user since ACT! for DOS v1.0 (1988)
Highlighted
Administrator
Posts: 4,041
Country: United_Kingdom

Re: Search "Today" in date field not working in Act! Premium Version 19.1.63.0

Hi ptrombetta,

 

I have previously updated this defect with the comments posted here. The defect has not yet been targeted to an upcoming version or update, and can be considered still in the backlog.

 

I believe the reason for the medium priority on this defect is due to the availability of low-impact workarounds for the issue (using date/time fields instead of pure date fields). Have you considered swapping your field types to work around this issue?