ManipulationLibrary Discussions Rss Feed

New Post: Add Date Not working

mfriedenthal — Fri, 17 May 2013 13:39:11 GMT

Matias,

I was able to confirm your findings. I had other problems with this custom workflow step, related to the end-of-business-day hour, as noted above, but also, because the datetime being passed to a method is universal time and it needs to be local time.

I wrote my own plug-in to do the job. This is not difficult.

Here's the original code; the problem originates in the first line:

 if (start != DateTime.MinValue && DaysToAdd.Get<int>(executionContext) != 0)
            {
                result = start.AddYears(YearsToAdd.Get<int>(executionContext))
                              .AddMonths(MonthsToAdd.Get<int>(executionContext))
                              .AddDays((7*WeeksToAdd.Get<int>(executionContext)) + 
                                       DaysToAdd.Get<int>(executionContext))
                              .AddHours(HoursToAdd.Get<int>(executionContext))
                              .AddMinutes(MinutesToAdd.Get<int>(executionContext));
            }

            Result.Set(executionContext, result);

You can see the calculation only occurs if the Days Added is not equal to 0

New Post: Add Date Not working

matiasdevit — Thu, 16 May 2013 19:55:16 GMT

Hi! No, it's more simple. I'm not working with business days. Just days.
Let's say, in example:

6/1/2013

i try to add 2 months. But the date remains the same.

I just noticed that it only works when i add "months" AND "days".
If i only add "months", it doesn't work.
Thanks.

New Post: Add Date Not working

mfriedenthal — Thu, 16 May 2013 19:51:53 GMT

There is a built-in assumption of a 6:00 end-of-business day. Is this what you're running into?

New Post: Add Date Not working

matiasdevit — Thu, 16 May 2013 18:16:35 GMT

Hi! We're using the "Add Date" functionality just adding a number to a date and it doesn't seem to work.
Is that a registered issue?
Thanks.

New Post: Date - Add Working Hours when outside 08:00 to 18:00

andrewwhitmore — Tue, 14 May 2013 18:42:32 GMT

Hello

When I add 1 working hour to a datetime, which then causes that datetime to fall outside of working hours (08:00 to 18:00), I can see that the time is rolled forward to the next available working hour.

e.g. if I add 1 hour to 17:15 the time returned is actually 08:00 on the next working day, not 18:15.

However I am using this library to process SLA times for case completion. I would like to add 1 hour to a datatime which would then allocate all available minutes to the remaining working day

e.g. if I add 1 hour to 17:15 I would like the time returned to be 08:15 the next day.

Is this at all possible?

New Post: does it work on CRM 2011 online ?

mpiccagli — Thu, 11 Apr 2013 10:43:30 GMT

HI,
I would like to know if the library can work on CRM 2011 ONLINE (not on premise).
Someone have some details or exmples ?
thank you.
MP

New Post: Undocumented Feature in Business Days Date Add

MarkPurnell — Fri, 05 Apr 2013 16:20:18 GMT

It really wasn't a problem. Just knowing that the code specifically determines that 8:00am to 6:00pm as 'normal business hours' would have been helpful in my testing. The source code is available so if you are so inclined, you can update it to fit your needs...

New Post: Undocumented Feature in Business Days Date Add

mfriedenthal — Fri, 05 Apr 2013 15:53:34 GMT

Mark, did you ever find a solution for the problem you documented above? I am trying to add x-number of hours to current process time nad sometimes it works and sometimes it doesn't. When it doesn't, I get a result of the following morning, or, if it's a Friday, the following Monday morning. If the function is relying on a CRM setting to determine what "normal business hours" are, where in CRM can I change that setting?

If I use the other utility, to just add (non-business) days, it doesn't seem to work at all.

New Post: Using Convert value in AddDays

carltoncolter — Sun, 03 Feb 2013 20:15:29 GMT

The line that sets the value should be:

var value = Convert.ToDouble(Value.Get<string>(executionContext));

not

var value = Convert.ToDouble(Value);

New Post: Undocumented Feature in Business Days Date Add

MarkPurnell — Wed, 14 Nov 2012 19:13:56 GMT

The Business Days Add function has a little bit of logic that will push the time out to 'normal business hours' (8am to 6pm) if it determines that your calculated date/time is outside of those boundaries.

That little feature was driving me nuts. It isn't documented in the guide, but should be.

New Post: RegEx Replace

NateOne — Mon, 20 Aug 2012 07:03:55 GMT

Carlton,

I would like to remove white spaces from phone number and save them to a separate field for searchabilty.

What Syntax should I use for that? I tried leaving the Replacement field blank and the Regular Expression Patter as /s but that doesn't seem to work...

See my setup here; http://sdrv.ms/OPbSBZ

thanks!

New Post: Using Convert value in AddDays

NateOne — Mon, 20 Aug 2012 06:55:49 GMT

I've had the same problem.

New Post: Using Convert value in AddDays

kknock — Tue, 29 May 2012 23:26:08 GMT

I'm trying to use the Convert Value Result in the Add Days function to create a new date value from a string field, but it isn't working. The convert value always comes up as zero.

The string is 010.

Any ideas?

New Post: Registration error

1sabine8 — Fri, 25 May 2012 13:25:58 GMT

Hi,

I'm trying to register this custom workflow and I get the error: 'Inner Exception: System.NotSupportedException: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. '

I found on a blog saying that in this case I need to Unblock the file and I did it but it didn't work.

Any idea of how I can solve this?

Thank you

New Post: Skipping weekends possible?

dsnuckel — Mon, 14 May 2012 20:02:57 GMT

I have a need to create a workflow which will create Phone Call records for a certain amount of days in advance based on a trigger of some other event. The problem is, I need to be able to skip the weekends. So, if the Phone Call record is created via workflow, and the Due Date is set to 3 days ahead. Can your workflow tool catch if that date is a weekend and adjust it to the following Monday instead?

Thanks

New Post: Process Time out seems not to support results from date time operations

DamonMKirk — Fri, 11 May 2012 15:57:21 GMT

I am having the same issue. Is there a fix or work-around for this?

New Post: Parse Date CRM 2011

carltoncolter — Thu, 03 May 2012 16:42:48 GMT

This will be fixed in the next update.

New Post: Parse Date CRM 2011

mxg0d — Wed, 22 Feb 2012 19:54:42 GMT

I noticed when using parse date, the year gets a comma put in it (ex 2,012) because it is an integer type. I manually added another OutArgument called YearString (so it doesn't break anything using year) so I could get the year to format properly. Is there a way to have it not display the comma?

New Post: Cannot Update Previous Version

mxg0d — Wed, 18 Jan 2012 17:59:33 GMT

OK. I tried changing the function names back and that didn't work.

The best way is to import the new solution that is included in the zip. Then in the customizations -> Manipulation Library (old version in my case 1.0.1.0) go to each workflow step and click show dependencies. Then change the version of the step to the new version (in this case 1.1). Looks like this from technet http://technet.microsoft.com/en-us/library/gg328011.aspx. In the case of "Add Days To Date" and "Sub Days From Date", you need to just delete that step and change it to use "Add Days" and "Subtract Days". That seemed to work for me. Once all the workflows are updated, you can delete the old version.

It is nice that they now have the show dependencies.

New Post: Cannot Update Previous Version

mxg0d — Wed, 18 Jan 2012 17:01:36 GMT

That didn't work. It gives me a cannot insert duplicate key error. I tried even converting this to a Managed solution for the DLL and incrementing the version, but I still get the same error. I have a feeling that it has something to do with the function for AddDays and SubDays being changed. I might try and compile a version of it with the old names for those funtion and see if that works.