IntenseDebate

1 year ago @ Pedro Innecco - Wii U Haxchi and CBHC:... · 0 replies · +1 points

You will be better off asking for help at this group: https://www.facebook.com/groups/534583420611589

6 years ago @ Pedro Innecco - The Business Intellige... · 0 replies · +1 points

What you just shared is a definition on what Business Intelligence is. What I am defining in this post is the disciplines that comprise business intelligence.

8 years ago @ Pedro Innecco - Dynamics CRM: The impo... · 0 replies · +1 points

Well... If that is an existing customer, it means that there has already been a past opportunity that sealed this lead into becoming a customer. So to me in this case it wouldn't make much sense to know in every opportunity from where that customer came from. I would rather consult the customer record (e.g. account or contact) for that information.

It is worth noticing that sometimes it is important to create new leads for companies that might already exist as an account in the system -- but it is a new department, division or business unit altogether. Hope this helps. Regards, P.

8 years ago @ Pedro Innecco - Windows 10 and Microso... · 0 replies · +2 points

The email still shows even for those using Windows Hello to log-in. The issue is that Windows shows the email address to identify an account as being a Microsoft Account.

As for the round pictures, so did Google and Apple, by the way. Funny how those companies try to be different form one another while copying one another. Sigh...

8 years ago @ Pedro Innecco - Lead entity changes in... · 0 replies · +2 points

Hi Daniel,

Well, you could do it by having a workflow that re-opens the lead after it is closed. You could do some conditional check on the workflow to find out whether the lead was closed automatically by the qualifying process or not. For example, if the lead has a related Opportunity.

However I would strongly suggest that you do not do that. Once a lead has been qualified, I see no reason to edit it -- unless it is to correct some fundamental mistake.

Regards,
P.

8 years ago @ Pedro Innecco - Dynamics CRM: Disablin... · 0 replies · +2 points

Hi,

In this example all scripts go in the form for the Opportunity entity. Bear in mind that this article was wrote for Dynamics CRM 2011.

Now for Dynamics CRM 2013 and onward, Microsoft changed the Opportunity for so you specify both the account and the contact. If only a contact is specified, then the contact is the customer. Otherwise the account will be specified as the customer regardless if a contact is also specified or not.

9 years ago @ Pedro Innecco - Dynamics CRM: Disablin... · 0 replies · +2 points

Hi Alec,

You could do that BUT that adds a new field in the entity which could create confusion for users using advanced find. Also in many cases the customer field can't be removed from the form and is a required field, which requires us to hide the field (or hack the XML customisafion file to remove it) and making sure that the field is no longer business required. Also I have to say that this post was mostly an exercise in Javascript indulgence ;)

9 years ago @ Pedro Innecco - Dynamics CRM 2015: My ... · 0 replies · +3 points

The only problem with real-time workflows is that they are evaluated at the saving of a record (i.e. creation or modification). If we want to have some logic that is triggered at the onChange event of a control, then we must use java scripts or business rules.

Also I hope that in the future Microsoft adds support to other events besides onChange.

9 years ago @ Pedro Innecco - Dynamics CRM 2015: My ... · 0 replies · +2 points

Hi Adam,

I have not tried the Business Rules on the tablet clients so what I was doing is putting A and B together, being both "A" and "B" feedback that I got from Microsoft on the Connect site. One thing that is clearly specified by Microsoft is that Business Rule logic can now be evaluated at the server-side.

9 years ago @ Pedro Innecco - Dynamics CRM 2013: Div... · 0 replies · +1 points

Hi Natasha,

If I understood correctly, you want to find out the stages in which an opportunity is at through the advanced find, and the relevant fields that have been for the specific stages, is that correct?

The first thing to tackle is the field that defines the stage in which your opportunity is at. If you followed the full tutorial series, we identified a bunch of fields that can help you with that. There is one particular field named Pipeline Phase (stepname) which is populated with the stage name prefixed by its ordinal position (e.g. "1-Prospect").

As for the fields have been filled against that opportunity, you should be able to create a view that contains the most important columns for opportunity records overall. However the challenge is when we have fields which are pertinent only at certain phases. For instance, we might have a date field with a deadline date for the submission of tender response which is only relevant to phase 3. For this reason, I would often add a custom view to list opportunities with relevant field for each phase. Hope that helps!

IntenseDebate Comment System

Connect with pmdci

My blogs/sites

People I'm following

pmdci