Hi Gilles,

Where would you recommend adding a Scheduler class within the Store Module source?  The plan is to use the scheduler to syncronize product data from a 3rd party source.

Thanks,

Jay

Hi Jay,

The SqlDataProvider IS NOT the right place! You have to use the DNN scheduler to add this feature. First, read the official documentation about the scheduler. Second, read this article about how to create a scheduler class, and may be this blog post about special case. The best place to add this class is inside the DotNetNuke.Store.Catalog project. If you name your class ProductsScheduler, the full class name (including Namespace) and assembly setting in the DNN Scheduler should be something like: DotNetNuke.Modules.Store.Catalog.ProductsScheduler, DotNetNuke.Modules.Store.Catalog. It use your namespace and class name followed by the assembly name. From within your scheduler class, you should connect to your external data source, then create an instance of CategoryControler and ProductControler to manage your categories and products.

Gilles

---

We (team members) are Humans offering their knowledge, their work and their spare time FOR FREE to benefit the community. It would be so particularly appreciated that your messages begin with "Hello" and end with "Thank you" or any other form of politeness. Ask yourself what your reaction would be, if you were approached by me (a total stranger) on the street to ask you something without saying "Hello" nor "Thank you"? After several years of services dedicated to the community, I begin to be tired to read requests without any form of politeness.

Hi Jay,

You'r welcome! A clasic dnn module is based on a three-tier architecture. The first level is the UI (your ascx controls). The second is the Business Logic Layer (BLL). Below the BLL, you should have an Abstract Data Provider (the DataProvider class). This allow you to disconnect your module from a specific database. In facts, it's an abstraction class to define how to access your data (something like a contract). The third level is the Data Access Level. This class is the SqlDataProvider project (or class) and his methods overrides those defined in the Abstract Data Provider. This allow some third party vendors like AcuitiSolutions to provide an access to Oracle database. They "just" have to re-write the SqlDataProvider with specific SQL commands for Oracle to allow DotNetNuke to run on Oracle.

This is why the best place is the BLL. In your case the Catalog BLL (DotNetNuke.Modules.Store.Catalog)! :-)

Gilles

---

We (team members) are Humans offering their knowledge, their work and their spare time FOR FREE to benefit the community. It would be so particularly appreciated that your messages begin with "Hello" and end with "Thank you" or any other form of politeness. Ask yourself what your reaction would be, if you were approached by me (a total stranger) on the street to ask you something without saying "Hello" nor "Thank you"? After several years of services dedicated to the community, I begin to be tired to read requests without any form of politeness.