Xpert360Lightning for Dynamics CRM


Xpert360Lightning for Dynamics CRM is a Lightswitch Data Extension that enables access to Microsoft Dynamics CRM Online or On-Premise (CRM 2011 only).

(4) Review
Visual Studio
2015, 2013, 2012
Download (3,105)
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Reviews (4)
Q and A (6)
Sign in to write a review
Sort by:

by Killizone | June 28 2012

by Jermanic | April 09 2012

Xpert360 April 18 2012
| Edit |


Thanks for the CRM online data adapter!

Xpert360 April 08 2012
| Edit |

No problem. Let us know what you think as we plan to release next version by end of April. Any entities you would like in particular or any 'big' data to work with. Thx

by Oliver Michalski | April 04 2012

Thanks :-)

Xpert360 April 08 2012
| Edit |

Would you like support for different security models or on-premise version, let us know, thx.

Sign in to start a discussion

  • Could I execute workflows with this connector?
    2 Posts | Last post October 21, 2015
    • I was wondering if it's posible to run on demand workflows from this connector...
    • Sorry but that is not built into the free adapter.
  • I don't understand the licensing.
    2 Posts | Last post December 31, 2013
    • Hi, I'm confused on the licensing, particularly: "Based on ‘Live ID’ to be used to access Dynamics CRM Online and ‘Organization Name’ used for the subscription."
      Is the licence required only once for Visual Studio as an extension only, or does the connector generate a licence on the files generated so acts as a mediator between CRM and your files on a webserver?
    • The license is based on the credentials for accessing the Dynamics CRM data. It is not checked when in the Visual Studio IDE.
  • ambiguous errors
    2 Posts | Last post November 27, 2013
    • Hi,
      I am continuously getting this error both on VS2012 and VS2013:
      'ComponentState' is ambiguous because multiple kinds of members with this name exist in class 'Xpert360Lightning.Role'.	
      'ComponentState' is ambiguous because multiple kinds of members with this name exist in class 'Xpert360Lightning.Workflow'.	
      Are you able to assist please.
    • Apologies for that. The Role entity has two conflicting property names, a column and an enum. To work around this always deselect the 'Role' entity in the attached data source dialog.
      We will correct this in the next maintenance release due next week.
      Thanks for reporting the problem
  • CRM 2013 and Custom Entities
    2 Posts | Last post October 16, 2013
    • Xper360 looks great.  Does it support custom entities?  Also, what is the status for CRM 2013?  
    • Hi David,
      It does not support custom entities in the community edition CE. We do a service to supply custom adapters to people to cover that. I am using the latest preview of the adapter here against CRM 2013. We are looking to release a new CE version soon after VS2013 RTM is available (18/10/2013).
      We plan on providing a commercial subscription-based Cloud version that is being tested and demonstrated today. This will be available in a few weeks too.
  • on-premise version please!
    3 Posts | Last post December 06, 2012
    • Is there a version I can try with an Dynamics CRM 2011 on-premise?
    • Unfortunately not with the first release. We are enabling alternative authentication methods with the next version, e.g. AD, so it will work with Dynamics CRM 2011 on-premise. We are interested in recruiting more people to try the on-premise version if you are interested. We need to know you authentication/security requirements and if any more entities are urgent. The first release included 40 entities for testing, the next release is still open so we can include more, for instance entities for the service module. 
    • Version 1.2 supports Dynamics CRM 2011 On-Premise with AD.
  • Which Dynamics CRM entities are you interested in accessing?
    1 Posts | Last post October 24, 2012
    • We gathering feedback as to whether a smaller more feature rich adapter would be useful to people. Perhaps one based around the Contact entity, for example. All feedback welcome!