This modification requires some basic CRM customizations, re-generating your xrm.cs file, and making appropriate changes to your code based on the other two example pages I gave. I am not comfortable in setting the expectation that a non-developer
can just copy/paste the code and it magically start working. The problem is not difficult, but I would recommend that a developer make the modifications.
The KB article code your developer should look at is:
var kbarticles = XrmContext.KbArticleSet.Where(k => k.StateCode == (int)Enums.KbArticleState.Published && k.msa_publishtoweb == true);
- notice that it is filtering by a custom attribute msa_publishtoweb. That attribute was added to the knowledge base article entity in CRM as part of the portal solution.
The notes on a case are filtered by a string variable. The case notes are rendered with a LinqDataSource which is a different mechanism than the static binding for a generic search for KB articles. Here is the code for the cases that does the
filtering:
<asp:LinqDataSource ID="CrmNoteSource" runat="server" ContextTypeName="Xrm.XrmServiceContext" TableName="AnnotationSet"
Where="ObjectId.Id == @CaseID && NoteText.Contains(@Filter)" OrderBy="CreatedOn DESC" OnSelecting="LinqDataSourceSelecting">
<WhereParameters>
<asp:QueryStringParameter Name="CaseID" QueryStringField="CaseID" DefaultValue="00000000-0000-0000-0000-000000000000" DbType="Guid" />
</WhereParameters>
</asp:LinqDataSource>
The filter parameter is set in the code behind as follows:
var parameter = new Parameter("Filter", DbType.String, "*WEB*");
Shan McArthur www.shanmcarthur.net Check out the commercial edition of xRM portals @ www.adxstudio.com
