Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I have a need to access Dynamics CRM data in a custom app. Is common data service is the right approach to achieve this? There is a need to read & write data from CRM entities, is CDS support write operation on CRM entities through APIs? Any other alternative approaches which should be considered for scale and performance over CDS? Any pointers for initial setup of CDS against a particular CRM org will be very helpful.
All I see from your question is Building an app with Dynamics CRM as datasource. Based on the enterprise data flow size, transaction scaling, security entitlements & available resource skill set - you have to decide the technology and architecture.
PowerApps (Canvas app) is low-code responsive app designer with Dynamics connector for two way dataflow, whereas Model-driven PowerApp is also cross-platform, cross-browser, responsive native app with strong security model built on top of Dynamics CRM system. Both should be scalable.
You can build app using React, Angular, Bootstrap technologies along with Dynamics CRM RESTful web api for CRUD operations to CRM entities.
You need CDS when you have multiple Dynamics ERP products like CRM, Finance & Operations and need to maintain the integrity of data between the system entities.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
Many vendors such as Microsoft with Sharepoint and Dynamics have made it impossible to access database tables directly in newer versions as they convert to Software as Service (SAS) offerings.
I am working with PTC Windchill and have developed extensive Oracle SQL Layer ETL processing. Is this a future proof practice within the context of this product line? Or in the future will I be required to work through some sort of DAL. If so, is there a recommended practice?
The information available from Windchill for Cloud appear vague and mostly suggesting to me virtualizion at the infrastructure layer, suggesting I would be able to query at the database layer for many years to come. Any confirmation, pointers or feedback would be appreciated.
Windchill offers extensive APIs for data access (and customization) in java. Starting from version 11.0, There are also some soap and rest web service for data access , but not for everything. It is always better to use API, they offer Data Abstraction Layer in a supported way. PTC would recommend that you refer to a consultant for this job.
But if you want to try:
There is a huge documentation about Windchill Customization, you can also create your own web services in java to access the data you want, if standard web services does not suffice. a starting point can be the Windchill help, and the javadoc located in the windchill server in this folder:
WINDCHILL_HOME/codebase/wt/clients/library/api/index.html
there are also some examples:
WINDCHILL_HOME/prog_examples
more documentation and appropriate training is available on https://support.ptc.com, only for registered customer users.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I am creating a web app using one of mean.io or mean.js for a mobile web site. From my mobile apps I want to be able to create users of this app using rest web services. I want to access the mongodb with crud operations using restful api. With mean.io or mean.js do you get these services for free? or how would you implement them? I know express is part of this but I have not seen how exactly with mean stack you access these services. Assuming basic add/remove user is provided with mean.io or mean.js I would still like to know how to add more rest accessible services like say inventory etc that is linked to the user. Could someone point me in the right direction on this? Also is there difference between mean.io and mean.js in terms of rest services available by default and adding more rest services?
Don't bother just use strongloop.io
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
For people who follow the fairly new ASP.NET Web API, they know that it is a good framework for building well-designed and outwardly-facing HTTP services that can span across many different clients using standard XML or JSON content types.
I have been recently designing a large API to be used with both a web and mobile clients. I noticed that within the ASP.NET Web API template provided through Microsoft's NuGet packages for Web API, they take a very minimal approach into Views with a slightly pretty homepage.
This took me back in a way. Mainly because I would assume that the Web API is designed for exactly that, a Web API, and nothing else.
In other's opinions, is it standard to develop the web client (that interfaces with your API)
Inside the Web API project?
Or
Outside the Web API Project to separate the web client just as you would your mobile or desktop clients?
The second choice seems logical to me in ways of maintainability and code-cleanliness, but there may be other perspectives that could be beneficial when designing in ASP.NET Web API. What do you think?
Great to see you using Web API!
About your first issue, you're right that it conceptually makes sense to separate Web APIs from views. I'd recommend either using the "Empty" project type in the MVC new project dialog and then adding API controllers. Or adding the NuGet packages yourself to an empty web project. The packages shouldn't be adding any views to your project.
Concerning clients, I'd strongly recommend separating out a client library to a separate project for maintainability. It's fine to have common data types that you share between the client and the Web API though. In that case, it's a common pattern to move your models to a separate dll, and have both the client and the Web API reference the types in that library.
A couple reasons you'd want the client and the Web API to be separate (and there are many more):
If you distribute the library, you want to distribute the client code and not the Web API code
You want to create a clean contract between the client and the server and avoid having the client depend on the server implementation or vice versa.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
Have any body integrated ERP with magento like (SAP,Jd edwards) .
IS It Possible?
What things one must know to integrate ERP system with magento?
I can tell from JDE Side.
If you are using Latest Version of JD Edwards then you can use Business Services in JD Edwards these are written into JAVA.
If you are using older versions of JDE which does not support its little complicated. You need to populate records in Table which can use by both JDE and Magento and use scheduler Reports to upload data in JDE (using EDI Module may be).
You need to define strategy how you are going to pass data to and from Magento to JDE and keep them in Synch (Order Data and Inventory data and Advanced Pricing). This step is important because you need to keep in mind that magento and JD Edwards both have there separate Order management, Inventory Management and Advanced Pricing Module.
I have seen lot of failure when it comes to JDE or SAP talking with External Systems which has their own similar module.
JD Edwards is really complex ERP so dont even think about or passing data by yourself. You will need functional Expert who knows about functional aspects and JDE Technical who can handle business Service task and knows how to use JD Edwards Tool set.
Hope this is Helpfull :)
Yes, it's possible. There is many different ways to integrate them. Anyway, you will have to write code on the ERP side or on the Magento side or on both sides together. Magento has an API to create products, orders etc. More of Magento API can be found here: http://www.magentocommerce.com/support/magento_core_api
You should be able to use Application Interface Server and Business Services Server to make inbound REST/SOAP calls and use Real Time Events for outbound calls to integrate JDEdwards EntepriseOne with third party system like magento. review the JDE Introperability guide.
https://docs.oracle.com/cd/E53430_01/nav/interoperability.htm
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
The question itself is very tricky. But I'll try to break it down into pieces.
Let's say I have external datasources each of them providing my data model. Either a webservice, or database. What matters is that my Entities are defined and exists in separated systems than the Dynamics builtin database.
What I want to do is to use the capabilities of CRM, to handle Business Entities (Provided from the external source), aspects such as security, and UI. Are well managed inside the CRM. So I want to build my system, using this tool, but I want to be able to store and keep the data in my own sources.
In other words, is there a way in CRM (Through the webServices I believe), in which I can provide the entity, and have it managed later inside the CRM.
thanks in advance... I really hope I can find the answer here.
The only option you have is to synchronize the data stored inside Dynamics CRM database with your external sources.
With tools like Scribe from Scribesoft, this scenario is manageable.
About 50% of the functionality of MS CRM is implemented via rather convoluted SQL views/queries/stored functions etc. It is much more then a simple "table per entity type" data store. There is no way to keep live data "somewhere else", so you are stuck with import/export (as recommended in the previous answer).