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?
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
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.
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.