Changing data source form SharePoint list to SQL table

Hi Eslam,

I haven't tested this but I believe this is possible by changing the service object method bindings.

Edit you smartobject in the designer or K2 studio, select a method and edit it

then change the service object method

I believe the Service object method itself is not editable from K2 Designer; this is how K2 "sees" this object from which ever back-ends it is; the edit will need to be made on the back-end.

So if the data source is now SQL instead of Sharepoint, was a SQL server service instance created?

http://help.k2.com/onlinehelp/k2blackpearl/userguide/current/webframe.html#WS_SQL_01.html

If this list was recreated as a SQL table, usuallly the Table Service Object will have a list method that you can map to this get list item method.  Then the Smartobject Properties and Service Object properties will need to be mapped accordingly.

Yes, you can do it one of two ways. Either edit the smart object in the Web Designer or in a thick client designer. I actually prefer the 2nd method using the thick client designer due to the stability of the tool and you actually get to work with a physical file that you can make a backup of before making changes to give you an opportunity to roll back if necessary. The key here is to not change the method or properties names on the smart object itself. 

Launch K2 Studio or Visual Studio and start a new blank project. I would name the project the same name as the category where your smart object lives today if you want it to show up in the same place. It isn't critical as the category structure is purely to organize for human understanding and isn't referenced when the product is looking for a smart object. That is done by System Name and/or GUID of the SmO.

In the new blank project, you will open the K2 Object Browser, find the smart object you want to change, right click and choose Save to Local.

A couple of key points about this approach that makes it desirable is that you can:

1. Make a copy of the SODX and put it in a safe place before you make changes. Making changes in the Web Designer updates your only copy so you mess up you are in trouble. Since you desire is to preserve the integrity of your solution while you make this change, having a back out plan is the way to go.
2. The changes you are making to the SmO do not become available until you deploy. So your solution will continue to function normally using the SharePoint configuration until you deploy the changes you have made in the design tool.

I used to acutally mention and teach this capability in my training classes as it is good approach to map out a data structure if the actual data sources aren't readily available.

Hope this helps.

S.