Dynamics 365 - 'PluginAssembly' entity doesn't contain attribute - dynamic

When create a connection using PluginRegistration, I was getting the error below.
'PluginAssembly' entity doesn't contain attribute with Name = 'packageid' and NameMapping = 'Platform'.
Can you offer a solution ? Thank you.enter image description here

Recently Plugin Registration Tool added new features and if the user used to connect has not a System Administrator role errors can happen.
I don't know if it is related to your case but I will check the roles first.
Also XrmToolBox has a Plugin Registration Tool (you can find it inside the Tool Library) you can try with this version and see if you can connect or not.

Related

TIBCO SPOTFIRE : Redirect Dependent Elements

I'm searching for a way to switch from a test to a prod1, prod2 and prod3 environments having same structure, but the schemas have different names.
Is it possible to do it with the same analysis that will be opened later with a Spotfire web clients (Dedicated for each environments )
I found this in the Doc, but as i said i need something configurable depending on the environment
EDIT
DATASource name : DbParc,
username : DB_PARC2.
So for example when using this analysis in an env with username DB_3, the information link or Procedure element will still use DB_PARC2
Thanks 4 any Advices..
You can create a dashboard (dxp) that has its own set of Information Links and its own set of datasources objects. You need to have all those objects in one folder.
Then you can use Library Administration tool and take Copy action.
You pick the destination and confirm Copy action.
The newly created folder will contain newly created dashboard and what is essential, the dashboad and its Info Links and column objects etc (all depenedcies of the dashboard) will be connectd to the newly created/copied data sources. Now you can change the datasource specific information as per your needs.
You should be able to do this using the (SOAP) Web Services API: https://docs.tibco.com/pub/spotfire_server/7.14.0/doc/api/TIB_sfire_server_WebServices_API_Reference/index.html
There is also an Automation Services task that might be useful: https://docs.tibco.com/pub/sfire_autsvcs/7.14.0/doc/html/TIB_sfire_autsvcs_7.14.0_UserGuide/GUID-A7A5FC46-2DC1-4E70-81F4-B34476AE9221.html

Azure mobile app with existing sql backend

I have been following these examples in a previous stack overflow example, I need to convert to an Integer id to an Azure mobile app, and need a MappingDomainManager class described by user Kiske1 in the post below.
Azure Mobile App using existing database
However, I have been unable to complete this as Automapper.impl.PropertyAccessor is “Type of namespace Impl does not exist…” I am using the latest Automapper dll v6.1.1.0.
Does anyone know where PropertyAccessor has been moved to/or replaced with?
Also, both examples that were specified in this post are from 2014, does anyone know of a more up to date walkthrough and preferably an example project?
Does anyone know where PropertyAccessor has been moved to/or replaced with?
I searched at AutoMapper project and found that PropertyAccessor has been removed. Also, I checked my mobile app project and the Automapper version is 3.3.1, the PropertyAccessor exists and the old sample could work. I assumed that you could try to downgrade the version of your Automapper to fix this issue.
does anyone know of a more up to date walkthrough and preferably an example project?
For Automapper 6.1.1, the usage for FindTypeMapFor method and the parameter type for GetExistingPropertyMapFor method have changed, you could modify your code under SimpleMappedEntityDomainManager as follows:
var m = Mapper.FindTypeMapFor<TModel, TData>();
m.GetExistingPropertyMapFor(new PropertyAccessor(typeof(TData).GetProperty("Id")));
To
var m = Mapper.Configuration.FindTypeMapFor<TModel, TData>();
m.GetExistingPropertyMapFor(typeof(TData).GetProperty("Id"));
Moreover, you could refer to adrian hall's book about The Domain Manager.

Create issue : Test link integration with jira

I've integrated Testlink with Jira using below xml
<issuetracker>
<username>xyz</username>
<password>#123</password>
<uribase>abc.net/projects/KEY/</uribase>
<uriapi>abc.net/rest/api/latest/</uriapi>
<uriview>abc.net/browse/</uriview>
<projectkey>KEY</projectkey>
<issuetype>1</issuetype>
</issuetracker>
I am able to link existing jira issue in to test link.
But create issue window contains Version field which would not alow me to enter any value or not giving any suggestion as displayed in below image.
I've tried to create version in jira but it doesn't work.
So,
What value i should enter/configure for version field ?
What is use of <issuetype>1</issuetype> ? can we provide any other value?
How to link new field on create Issue window?
4.Version is mismatched with jira field Versions.
I'm not sure which version of JIRA REST API you are using but the tutorial for the v2 says:
Just like everyone else in the real world, we're faced with time and resource constraints. Supporting two serialisation formats requires more time than just a single one. Hence, for our initial release of the JIRA REST API, we decided to provide "more stuff in JSON" rather than "less stuff in JSON and XML".
So I'm not sure about the XML support. I have no experience with Testlink, but I guess it's using some kind of serialiser at the back end.
If you check the Create issue endpoint, there is no version field. I guess it will be the versions field instead. In JIRA projects can have multiple versions. You can get a list of versions from the Get project eversions endpoint.
Issue type is an ID of issue type you want to use for your issue. You can get a list of project specific issue types from the Get issue all types
endpoint.
I'm not sure about this
Check the first point
This version field is empty because you have not specified any version for your project in JIRA. In my case it was Fix version in JIRA. Currently the rest API is getting an empty list of versions. You can try
curl -X GET http://example.com/rest/api/2/project/KEY/versions
-H 'authorization: Basic dtgzkisVlbyhsuYWhtYijdsdidjjsidDkw'
This will give you an empty list.
Once you set FixVersion in for your project in JIRA, this API will return the list of available versions for your project and the Version field will be populated with those versions.
PS: use your own authorization headers. You can use [Postman][1] for this purpose.

How to retrieve Salesforce Page Layout Field Properties via API?

Context:
The Web interface coded in .NET (Grantee Portal for nonprofits applying for grants) is pulling information from the Salesforce Page Layout.
The Salesforce user we use to connect the Web interface with Salesforce via API has 'view all and edit all' rights
Issue:
As it is now, if a field is defined as Read-Only on the Page Layout in Salesforce, it is still editable on the web page (the Salesforce User we use has to have 'view all and edit all' rights)
What we are trying to achieve:
IF a field is defined as Read-Only on the Salesforce Page Layout
THEN the same field should be Read-Only on the Web interface page
Question:
To achieve the above, I guess that I need to fetch the field property for the Page Layout via API. Any ideas on how to do so?
Thank you!
Izumi.
You'll need Metadata API (the set of webservices that let you add new objects, fields, picklist values or even create classes & run unit tests).
Here's the API Guide: http://www.salesforce.com/us/developer/docs/api_meta/index.htm
Depending on how often you modify layouts you might decide "screw it, I'll just use Eclipse IDE". In that case you'd download all page layouts (they're XML files), point your C# app to them and let the magic happen.
Slightly more advanced is to use Migration Tool (Ant / Java based application that can be scripted for periodic download of same stuff).
Super advanced would be to use this API guide to write it in C#. It's not rocket science (here's the specification for Page Layout object and here's the Java sample code for the operation that retrieves the metadata... sorry, no C#). Actually you might be better off looking at this example though: http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_describelayout.htm
Seeing that you'll probably want to cache this info somewhere anyway (I can't imagine your user coming to your page, having to wait for the webservice callout to complete, then having his UI rendered) - pick your poison.
Or share the work within the team (1 person kicks off with files downloaded with Eclipse, other tries to figure out the C# code to retrieve them on demand).

Commentable plug-in with Spring Security LDAP

I'm trying to get the commentable plug-in running with the spring security framework ldap plugin from Burt Beckwith.
I found a similar problem here.
The only difference seems to be that I'm using LDAP and the LDAP user details don't have an id, or I'm not seeing it.
I've tried setting the grails.commentable.poster.evaluator to
{com.companyname.sec.User.get(org.springframework.security.core.context.SecurityContextHolder.context.authentication.principal.id)}
and also to
{com.companyname.sec.User.get(principal.id)}
Both of these were suggested in the other issue I referenced above. What I get is the error below:
groovy.lang.MissingPropertyException: No such property: id for class: org.springframework.security.ldap.userdetails.LdapUserDetailsImpl
Possible solutions: dn
This seems to suggest using the dn field, but since that's a string, and the id is a Long, I don't think that's the right option. So, is there a way to configure the grails.commentable.poster.evaluator to get these two plug-ins to work together, or do I need to modify one of them to get a compatible type (i.e. change the commentable plug-in to use a String, and then grab the username from the LDAP user details.)?
Not using the commentable but the spring-security-ldap plugin.
For me this really simple copy&paste solution worked:
Solution on Grails Jira by Burt
Use
{com.companyname.sec.User.findByUsername(principal.username)}
or
{com.companyname.sec.User.findByUsername(org.springframework.security.core.context.SecurityContextHolder.context.authentication.principal.username)}
That gives me the following error:
org.grails.comments.CommentException: No [grails.commentable.poster.evaluator] setting defined or the evaluator doesn't evaluate to an entity. Please define the evaluator correctly in grails-app/conf/Config.groovy or ensure commenting is secured via your security rules
I read that to mean there is no findByUsername method. So, were you suggesting I create that method in order to get at an id value? And I assume correspondingly, that means I need to insert the ldap users into the database in order to generate an id.