Custom content type and Reporting

Hi Iurii,

Your custom content would need to be implementing a plugin type which registers each content item.  Typically this occurs when the content is first created by implementing plugin types that fire when the content is created, such as IAbuseCheckingContentType, IActivityStoryContentType or ISearchableContentType.  Other plugin types only register the content when the content is interacted with, such as IBookmarkableContentType, ILikableContentType, etc...

I know. Our content implements a lot of contenttype's interfaces. Not all of possible, but a lot.
Is some specific must be implemented for Reporting?

There is nothing specific, it's just ensuring implementation of plugin types as I listed above.  

From your list I have implementation only 

ISearchableContentType

No, as long as ISearchableContentType is fully implemented and your custom content is being indexed by search without exceptions, then that should be all you need.  After the content is indexed, it is being registered with our core content service which allows it to be picked up by the Reporting ETL.

Would not implementing  IActivityStoryContentType mean it wouldn't appear in the Activity widget?

Yes, if you do not implement IActivityStoryContentType, for custom content, it will not create an activity story when new content is created.

Well.
I tested on my local and see same situation.

I found my custom content in ReportingDB in table [dbo].[StagingContent]
it does not have Name and Subject ('Unknown'). Also only part of CreateDates are same as content has, all other is a date of content generation (today).

In ETL logs see only one error line

Anyway, graphs are empty (my local instance is fresh and contains only my custom content). How I can troubleshoot that?

It looks like the database has not been updated to match the version of the ReportingETL.exe you are using.  

Reporting has very limited capabilities when it comes to custom content.  It has no idea where the content lives so it can only pull over what the core services know about the content, which is what is handed when ISearchableContentType, or one of the other plugin types, registers it.  You need to ensure that you're implementing IContent.  If you have this properly implemented, the date should match and while the name and subject will show ('Unknown'), when shown in reporting a lookup occurs that will show the IContent.HtmlName.

Okay. I made it work.
And see strange results. I created all contents (2000) at once. Than changed createdDate in DB with random values in 2 years interval.
Now on graph I see 1800 contents created in that 1 day and other 200 contents has random dates.
I clicked Reset and started ETL several times.

Can I reindex content with correct CreatedDate?

Okay. I made it work.
And see strange results. I created all contents (2000) at once. Than changed createdDate in DB with random values in 2 years interval.
Now on graph I see 1800 contents created in that 1 day and other 200 contents has random dates.
I clicked Reset and started ETL several times.

Can I reindex content with correct CreatedDate?

Brian Dooley Hi. 
I still have an issue.

On our production server we have thousands of custom contents, that created in few hours but have createdDates within 10 years.
First of all I can't select filters older then community lifetime (2 years).
Secondary - there is no custom our content at all. I tested on my local and can see it in Reporting with strange dates (described abouve).

So can I have a way to diagnose the problem? Can I force to re-index content? 

In our PROD Reporting table [dbo].[StagingContent] completely empty

You can reset your reporting.

(+) Why have my reports Flatlined? - User Documentation - Verint Community 12.x - Verint | Telligent Community

Brian Dooley said:

You can reset your reporting.

We've done this on a number of occasions, the ETL service is reporting that it has ran successfully.

I'd recommend opening a support case to look into the issue.

Makes sense.  I'll hit the reset button one more time to make sure.

Unfortunately I'm not seeing any change in these items failing to appear in reporting.