How To use Common Data Service (CDS) Power Apps with Model Driven Apps
How TosJoin Serge Luca, MVP, REDWOOD S.L SPRL, Belgium for this short video on How To use Common Data Service (CDS) Power Apps with Model Driven Apps
Join Serge Luca, MVP, REDWOOD S.L SPRL, Belgium for this short video on How To use Common Data Service (CDS) Power Apps with Model Driven Apps
We all have in recent times have been in a situations where we need to decide if any business application need to move to cloud. Have we not been talking about devops for long? Microsoft is moving into the DevOps space and they have an Ace up their sleeve. Learn from Azhar Amir an efficient Model for Microsoft based DevOps on Cloud.
Have you been playing with the SharePoint 2013 preview? What are your initial thoughts? That is, aside from the slick metro styling, deep office integrations and drag and drop capability, streamlined editing (the ugly context menu is fading away, my friends), and even a simplified ribbon interface – what stands out most to you? SharePoint 2010 was altogether a successful platform, but with the move toward the cloud, the influx of devices into the enterprise, and the “consumerization” of IT where end users drive the demand for what data and which tools are used to consume information. Microsoft listened to feedback from their customers, they made some decisions about the future of the platform, and they most definitely did something different. SharePoint 2013 is a platform of change. Its important to understand the real changes happening under the covers, impacting the direction of future versions – and most definitely your roadmap for using SharePoint going forward.
SharePoint 2013 introduces a new mechanism for custom code deployment known as “Apps”. Mostly targeted at online solutions, the purpose of the App model is to overcome the severe limitations of the 2010 isolated execution model (also known as the “Sandbox”) and provide developers with a way to run rich web applications in SharePoint without negatively impacting the underlying infrastructure. Much has already been made about this new model and a lot more will be written about it over the coming year as 2013 gets released and adoption spreads. Before we get too far off the beaten track into a debate about whether or not developers should or should not be using the new App model, it’s helpful to first understand why Microsoft chose this path and what it really means for both new application developers coming onto the platform and existing developers who need to support the next release.