I have an MVC application with one part of it deals with Stock/Store management. Odoo has a good stock management module, which if integrated with my application would handle the stock part of the software.
The application is developed with MVC, c# and the backend SQL server.
How can I integrate Odoo stock module with my application? I want to access (read and write) just the stock module through an api (RPC).
AFAIK only way you can achieve this is by running an instance of Odoo with its own postgresql database and all the modules on which stock module depends on installed.
Then you should use RPC to call not just stock module, but also other modules, such as product, in order to fill database with your products. Basically you will have to replicate a large part of your data over Odoo database.
You need to ask yourself if it's worth the trouble, maybe it would be faster (both in developing and in performance) to just replicate Odoo's stock management inside your own MVC.
Related
I'm starting a new project where we are expecting to migrate desktop based Access 2016 applications (with a lot of backend VBA and relationships between the tables) into SharePoint 2016 on-premise and very soon, SharePoint Online. From what I've been told, we'll be given site permission to a SharePoint site that we can do whatever we want with. I am hoping that with SharePoint 2016 on-premise and eventually SharePoint online means that there is a SQL Server and eventually Azure SQL Database that I can migrate the Access backend tables and queries, as I know SharePoint lists will be inadequate for this, despite the false notion that SharePoint lists are an equivalent substitute for database tables.
My concern is how to build the custom forms, perform the needed business logic, perform CRUD operations, and upload data in the form of Excel files from the SharePoint site to the backend.
I'm new to SharePoint and given that it does not support VBA, that Microsoft cut out Access Web Apps earlier this year, and they are phasing out SharePoint Designer 2013 and InfoPath, some research over the past week indicates my best options are building custom web application using ASP.NET Core and somehow deploying that to the SharePoint site and subsites that we have control over, or developing a lot of HTML, CSS, and JS to create the front-end interface. I had read about the Business Connectivity Service to get and post data to / from the SharePoint site front end and the DB backend, as well as using Javascript and AJAX calls to do CRUD operations between the database and the frontend. I looked into PowerApps and those seem insufficient, and I'm still trying to distinguish between SharePoint web parts and SharePoint add-ins.
Is any of the above even a feasible option? Could someone chime in on a better path to go about this? What technologies would I need to best go about this?
Support for moving tables from Access to SharePoint remains a choice and option.
So all of your VBA code etc. will work as before. The only real question is if you want to move your data to SharePoint tables in place of using SQL server.
SQL server tables are far faster than SharePoint tables.
However, you can certainly consider moving your tables to SharePoint. When you move your tables to SharePoint (or SQL server), then Access code, forms, reports etc. and EVEN your VBA code will work as before. What this means is that you continue to deploy the Access application to each desktop. The only difference is now your tables are on SharePoint, or SQL server.
The above choice does not result in a web based application.
So you can move the data, but your application will remain a desktop application.
If you looking to build a web based application, then Access is the wrong tool – you need to adopt something like Visual Studio.
So you can continue to use Access, and put the data tables into the cloud, or on-site SharePoint - but the application will be still desktop based.
I have used the following extensively over the last couple of years and I am happy with the experience:
Azure SQL Database as a back-end
Flow for automation and as an interface to the DB
PowerApps for forms, desktop apps and mobile apps
Excel for reporting (Get & Transform aka PowerQuery and DAX), especially for printing reports
Power BI for dashboards (limited use)
Yes, PowerApps has drawbacks, but there are a lot of realistic workarounds out there and new features/improvements are being added regularly.
I have also used SharePoint lists as data sources, but almost always then migrated to Azure SQL Database.
Is it possible to use use SharePoint to custom develop a GUI for an SQL Server backend for updating the data? Thanks.
If you are using SharePoint 2007 you might want to take a look at the Business Data Catalogue - http://msdn.microsoft.com/en-us/library/ms563661(v=office.12).aspx
Not sure what the comparable feature (if any) in 2010/2013 is...
EDIT:
In 2013 it is called Business Connectivity Services - http://msdn.microsoft.com/en-us/library/jj163782.aspx#BCSoverview_Whatcanbcsdo
Look at "Business Connectivity Services" and "External List".
SharePoint Designer can make the process pretty simple or you can develop a Visual Studio project:
http://msdn.microsoft.com/en-us/library/ee558778(v=office.14).aspx
If you want to do the legwork try building an Access Application in SharePoint 2013.
It is much better than 2010 but requires more setup. This will encapsulate a database within a SQL database, very versatile super quick and you can do all your SQL fun stuff from there.
This is a low or no code solution.
SharePoint 2010 Access apps use lists as back-end repositories, you can interact with the data in the SharePoint WSS_Content database, but it is not supported and no advisable.
Here's task: We have an sql server database. which is hosted at our server. What we need to do is: we need to create a non-techy-users interface (basically insert/edit forms) and let these non-techy-users to install this database locally, since they are located in the areas without internet connection. Then when they're done using the database we get the data from them and inster it in our database.
The biggest concern is that it is not trivial for non-it people to install sql server. Can you please advise me what solution should I choose? Simple Access should work fine, but i really do not want to mess with it and have data conversion back and forth between engines.
Sync Framework for SQL Server: your application uses a lite weight, embedded SQL Server CE (no installation, just a couple of DLLs deployed along with your app) and the sync framework manages the synchronization with the 'mother ship' SQL Server.
Out of interest, why do they need their own installation? Can't you create a new database on your existing instance?
If you're looking for an easy way to create insert/edit forms on your database, have you considered looking at Microsoft's new LightSwitch product (currently in Beta) or Microsoft's Dynamic Data?
I am trying to use WCF Services as models for SQL Server Reporting Services 2005 reports. I can do this if I design the reports in the designer but cannot do it for a Reporting Model project which I think I need to make reports in the Report Builder.
My full requirement is to have a report builder that the users can use building reports based on DTOs supplied from my WCF service.
Thanks
Turns out you can't do this.
I've gone for Dex Express XtraReports which seem to be more powerful. I'm using their designer components to make a Report Designer application - which I shall customise to integrate completely with the application - save/new/edit all handled by my code should make the experience more pleasent for the user.
It seems SSRS just isn't ready for user designed reports based on .NET objects yet.
I am looking to build some reports for Quickbooks data, without using Quickbooks built-in reporting, or through a third party library (like QODBC).
Quickbooks 2008 and newer are built on a SQL backend.. In looking around there seems to be several products and angles to do this from.
Ideally I would like to be able to do direct SQL hits on the database myself, or use something like Crystal Reports.
I wanted to ask here to gather any things to look at closer, and what to potentially avoid to save myself grief.
Thanks in Advance!
Update: It seems Quickbooks encrypts it's sql database so you can't read it directly with a reporting tool.. There are a few products on the market that can help.. more to come.
Your best bet is the QuickBooks SDK, it provides facilities to fetch data and also fetch reporting data directly from QuickBooks, formatted as XML for easy parsing and display however you want to display it.
You can see the data that's available using the qbXML/QBFC QuickBooks On-Screen reference (the requests you can send to QuickBooks are found in the 'Select Message' drop-down box at the top of the screen).
The QuickBooks SDK is a free download (registration required) from the Intuit Developer Network
If you're writing a desktop application, you can look into using QBFC, which is an API that talks to QuickBooks using COM/DCOM.
If you're using PHP, there's a popular QuickBooks PHP framework on the IDN forums.
If you're using ASP.NET, here's a QuickBooks ASP .NET framework too.
If you want direct SQL access, you should look at QODBC (which is an SQL wrapper which translates SQL queries to qbXML SDK requests) or AccessBooks (which uses the SDK to mirror QuickBooks data to an SQL database).
If its hosted on SQL 2005 or 2008 you can make use of Reporting Services (free) and the Report Builder that is bundled with it. If you use 2008 then I recommend downloading Report Builder 2.0
http://www.microsoft.com/downloads/details.aspx?familyid=9f783224-9871-4eea-b1d5-f3140a253db6
Here's some links to learn RS:
http://www.google.com/search?q=reporting+services+tutorial+video&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a
So are you on the 2008 edition (SQL Server)?
If so, you can use SSRS as SQLChicken posted, or you can use just about any other reporting tool, and connect via SQL Native Client (shipped with SQL Server):
- Crystal Reports
- Excel
- insert your favorite reporting tool here