News.mscrm-addons.com BlogHello and welcome to our blog! What can we do for you? Are you looking for further technical information or step-by-step instructions to our products? Or would you like to read the latest news on mscrm-addons? Please feel free to browse our blog for detailed information and to share our posts! https://www.mscrm-addons.com/BlogAdditonal Filter for PowerSearch Silverlight (Version 5.42 or higher)https://www.mscrm-addons.com/Blog/PostId/9683/additonal-filter-for-powersearchPowerSearch (PS),PS 2011Thu, 24 Oct 2013 14:05:00 GMT<p>When you search for big amounts of entities, a <em>SQL TimeOut exception</em> can occur. To minimize the amount of data, you can specify <em>additional filtering</em> in the <em>PowerSearch Configuration</em> (This filter must be manually inserted into the XML of the PowerSearch Config).</p> <p>To specify additional filtering, navigate to CRM &gt; Settings &gt; MSCRM-ADDONS.com Products &gt; PowerSearch &gt; MSCRM-ADDONS.com Settingkeys &gt; ServerConfig.&nbsp;</p> <p> <div class="lightbox" data-plugin-options="{'delegate': 'a', 'type': 'image', 'gallery': {'enabled': false}}"> <a title="PowerSearch Settings" href="http://mscrm-addons.com/images/blog/files/2013%2f10%2f001.PNG"> <img alt="" class="img-responsive" src="http://mscrm-addons.com/images/blog/files/2013%2f10%2f001.PNG" width="500" height="400" /></a> </div> </p> <p><em>Figure 1: PowerSearch Settings</em></p> <p>Edit the KeyValue as described in Figure 2 and below. &nbsp;</p> <p> <div class="lightbox" data-plugin-options="{'delegate': 'a', 'type': 'image', 'gallery': {'enabled': false}}"> <a title="Edit Key-Value" href="http://mscrm-addons.com/images/blog/files/2013%2f10%2f002.PNG"> <img alt="" class="img-responsive" src="http://mscrm-addons.com/images/blog/files/2013%2f10%2f002.PNG" width="500" height="300" /></a> </div> </p> <p><em>Figure 2: Edit Key-Value</em></p> <p> Between the tags of the entity you are planning to filter, add a<em> <additionalfilter></additionalfilter> </em>tag. Inside of the <em> <!--[CDATA[</em--> &nbsp;you can fill in your filter condition. (These are the same filter condition as in CRM.)</em> <em></em> </p> <p>&nbsp;</p> <p><strong>Example:</strong> (Show only mails from the last 10 weeks):&nbsp;</p> <p> &lt;email&gt;<br /> &nbsp;&nbsp;&nbsp; &lt;searchfields&gt;subject,description,regardingobjectid,torecipients,sender&lt;/searchfields&gt;<br /> &nbsp;&nbsp;&nbsp; &lt;resultfields&gt;subject,regardingobjectid,torecipients,sender&lt;/resultfields&gt;<br /> &nbsp;&nbsp;&nbsp; &lt;activestate&gt;1&lt;/activestate&gt;<br /> &nbsp;&nbsp;&nbsp; &lt;collapseonrow&gt;&lt;/collapseonrow&gt;<br /> &nbsp;&nbsp;&nbsp; &lt;sortorder&gt;&lt;/sortorder&gt;<br /> <strong>&nbsp;&nbsp;&nbsp; &lt;additionalfilter&gt;&lt;![CDATA[&lt;filter type="and"&gt;&lt;condition attribute="createdon" operator="last-x-weeks" value="10"&gt;]]&gt;&lt;/condition&gt;&lt;/additionalfilter&gt;</strong><br /> &lt;/email&gt; </p> <p>&nbsp;</p> <p>&nbsp;</p> <p>Finally click on the <em><strong>[Save]</strong></em>-button at the <em>PowerSearch Settingskey</em> to save your new filter on the entity.</p> <p>&nbsp;</p> <p><span style="color: #ff0000;"><strong>Please note:</strong></span></p> <p>If you want to create your own filter conditions easier, you can create the filter in the CRM&nbsp;<em>Advanced Find</em> and click on the <strong>[</strong><em><strong>Download Fetch XML]</strong></em>-button.</p> <p>Simply copy the filter condition inside the so received XML-file and paste it into the additional filter of the PowerSearch Config entity.</p> <p> <div class="lightbox" data-plugin-options="{'delegate': 'a', 'type': 'image', 'gallery': {'enabled': false}}"> <a title="CRM Advanced Find" href="http://mscrm-addons.com/images/blog/files/2013%2f10%2f003.PNG"> <img alt="" class="img-responsive" src="http://mscrm-addons.com/images/blog/files/2013%2f10%2f003.PNG" width="500" /></a> </div> </p> <p><em>Figure 3: CRM Advanced Find</em></p> <p><strong>That&rsquo;s it!</strong>&nbsp;We appreciate your feedback! Please share your thoughts by sending an email to&nbsp;<a href="mailto:support@mscrm-addons.com">support@mscrm-addons.com</a>.</p>9683Email messages take hours or even days to go out through the email router for MS CRM 4.0https://www.mscrm-addons.com/Blog/PostId/9511/email-take-hours-or-even-days-to-go-out-thru-the-email-router-for-ms-crm-40*General*Thu, 16 Dec 2010 17:13:00 GMT<p>We once had the problem that some emails with a long text in it were taking ages till they were send. We are using the email router to send and receive emails to our support team.</p> <p>As we moved some months ago from normal exchange to BPOS my first suggestion was that it has to do with the connection between BPOS and the Emailrouter. ( RU 14)</p> <p><strong>In the event-viewer I recognized the following entry:</strong></p> <p><em><span style="font-size: xx-small;">#61042 - An error occurred while the outgoing email message with the subject Re: urgent problem with DCP config PTM CRM00114110 CRM: 0000132293' for ExchangeOnline: </span></em><a href="http://[servername]/PTMEDVSystemeGmbH"><em><span style="font-size: xx-small;">http://[servername]/PTMEDVSystemeGmbH</span></em></a><em><span style="font-size: xx-small;"> for delivery through </span></em><a href="https://autodiscover-red002.mail.emea.microsoftonline.com/ews/Exchange.asmx"><em><span style="font-size: xx-small;">https://autodiscover-red002.mail.emea.microsoftonline.com/ews/Exchange.asmx</span></em></a><em><span style="font-size: xx-small;"> The request failed with HTTP status 413: request entity too large, <br /> at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)bei System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) bei Microsoft.Crm.Tools.Email.Providers.ExchangeServiceBinding.CreateItem(CreateItemType CreateItem1) bei Microsoft.Crm.Tools.Email.Providers.ExchangeOnlinePollingSendEmailProvider.SendMessage(MessageType mailMessage) bei Microsoft.Crm.Tools.Email.Providers.ExchangeOnlinePollingSendEmailProvider.ProcessMessageInternal(email emailMessage)</span></em></p> <p>So I created a case by Microsoft to let them look through this behavior. In this last month I was forwarded 3 times from the CRM team to the BPOS team and back. Today was the big day and the wonderful guy from the BPOS team was able to give the right hint with the following description in his email to me:</p> <p><em>For messages to be sent to Exchange Online through the Email Router for CRM, the Secure Sockets Layer certification must be enabled for Exchange Online and your Email Router to communicate. The default size for the buffer in the SQL Server is 48k and every email with more text results in error HTTP status 413: request entity too large.</em></p> <p><em>The solution to this is to logon to your SQL server and follow these instructions:</em></p> <p><em><strong>Increase the size of the UploadReadAheadSize property on your SQL server: </strong> <br /> - Click Start, click Run, type cmd, and then click on the <strong>[OK]</strong>-button. <br /> - At the command prompt, type the following: <br /> <br /> cscript adsutil.vbs set w3svc/1/uploadreadaheadsize 500000 <br /> <span style="color: #ff0000;">Please note: This command changes the UploadReadAheadSize property to 500 KB (500,000 bytes). </span> <br /> - Press the <strong>[ENTER]</strong>-button. <br /> - By running this command, you update the Microsoft Internet Information Services (IIS) metabase so that you can upload files that are as large as 500 KB. <br /> <span style="color: #ff0000;">Please note: In certain situations, you may have to set the UploadReadAheadSize property to even larger than 500 KB. </span></em></p> <p>In my case I had the <em>SQL Server</em> and the CRM Server on one machine and I executed this script and I was not able to reproduce the error. The conclusion is that this had nothing to do with BPOS and everyone also with a <em>normal</em> Exchange can come into this problems.</p> <p>The dangerous thing is that you do not realize that behavior easily, because you send your email from the web client and the email closes successfully. If you do not explicitly look for the email, you do not see that it was not send or delayed.</p> <p>If you have the same problem, I hope this will solve your issue too.</p> <p><strong>That&rsquo;s it!&nbsp;</strong>We appreciate your feedback! Please share your thoughts by sending an email to&nbsp;<a href="mailto:support@mscrm-addons.com">support@mscrm-addons.com</a>.</p>9511CTI in a hosted environmenthttps://www.mscrm-addons.com/Blog/PostId/9490/cti-in-a-hosted-environmentTelephoneIntegration (TI),TI 4.0Fri, 09 Jul 2010 11:29:00 GMT<p>CTI <strong>does</strong> need the server component in a hosted environment as well, but you can launch the CTI Server setup from any Client, as long as you have a user with full access to CRM.</p> <p>You need to select the hosted options on the Connection dialog.&nbsp;</p> <p>If you have physical access to the CRM server, you can simply launch the setup on that server as if it were an onPremise installation.</p> <p>Due to the mechanics of an IFD setup, the client will not use a SQL connection to retrieve the information, but a webservice call.</p> <p>As webservice calls are more limited as SQL queries, it is recommended to create a hidden field in CRM on the entities you want to search in.</p> <p>They will hold the numbers in a format similar to the one TAPI uses.</p> <p>You can achieve this either via an onSave script or via a workflow in CRM, transmuting the number to a TAPI compatible format.</p> <p>This is only required for caller identification, outbound calls will work with the formatted number, because they are processed by the Client application.</p> <p>&nbsp;</p> <p><strong>Explanation:</strong></p> <p>The number stored in CRM is formatted canonical, looking like +43 (316) 680880 0</p> <p>The TAPI drivers delivers a number as 00433166808800.</p> <p>Though the information is the same, the formatting prevents the CTI to find the number, as the webservice call is not able to resolve the formatting.</p> <p>If you have a field in the CRM entity that is getting filled with the unformatted number, you can setup the CTI to use that field for the lookup and get correct results in looking up the callers, but still have a well formatted number in the CRM to display.</p> <p>&nbsp;</p> <p><strong>That&rsquo;s it!</strong>&nbsp;We appreciate your feedback! Please share your thoughts by sending an email to&nbsp;<a href="mailto:support@mscrm-addons.com">support@mscrm-addons.com</a>.</p>9490