Discussions
File References Needed for IBO for .NET project
I am trying to upgrade our existing applications after upgrading imis to 20.2.65.9655.
Finding Event Pricing
Hello,
iMIS contact developer
Is there any way I can contact imis support directly?
Pulling list of Panel Sources
Is there a simple way to pull a list of sources (both single instance and multi-instance) other than looking for it in the ObjectMetaData and ObjectPropertyMetaData?
Please allow PUT at /api/Order_Badge endpoint.
Hello,
Creating a relationship
I queried a certain relationship with the REST API. This is production data:
{
"$type": "Asi.Soa.Membership.DataContracts.GroupMemberData, Asi.Contracts",
"MembershipDetails": {
"$type": "Asi.Soa.Membership.DataContracts.GroupMemberDetailDataCollection, Asi.Contracts",
"$values": [
{
"$type": "Asi.Soa.Membership.DataContracts.GroupMemberDetailData, Asi.Contracts",
"GroupMemberDetailId": "RELATIONSHIP-10548:2519:3168",
"Stage": {
"$type": "Asi.Soa.Membership.DataContracts.GroupStageData, Asi.Contracts"
},
"ExpirationDate": "2016-07-13T00:00:00",
"Role": {
"$type": "Asi.Soa.Membership.DataContracts.GroupRoleData, Asi.Contracts",
"DefaultReciprocalRoleId": "NPEEXH",
"DefaultReciprocalDescription": "NPE Exhibitor Contact",
"DefaultReciprocalName": "NPEEXH",
"RoleId": "RELATIONSHIP:NPEEXH",
"Description": "NPE Exhibitor Contact",
"Name": "NPEEXH"
},
"ReciprocalRole": {
"$type": "Asi.Soa.Membership.DataContracts.GroupRoleData, Asi.Contracts",
"DefaultReciprocalDescription": "NPE Exhibitor Contact",
"DefaultReciprocalName": "NPEEXH",
"RoleId": "RELATIONSHIP:NPEEXH",
"Description": "NPE Exhibitor Contact",
"Name": "NPEEXH"
},
"Title": ""
}
]
},
"GroupMemberId": "RELATIONSHIP-10548:2519",
"Group": {
"$type": "Asi.Soa.Membership.DataContracts.GroupSummaryData, Asi.Contracts",
"GroupId": "RELATIONSHIP-10548",
"Name": "C. Todd Reed Relationship",
"Description": "Relationships",
"ParentIdentity": {
"$type": "Asi.Soa.Core.DataContracts.IdentityData, Asi.Contracts",
"EntityTypeName": "Party",
"IdentityElements": {
"$type": "System.Collections.ObjectModel.Collection`1[[System.String, mscorlib]], mscorlib",
"$values": [
"10548"
]
}
},
"GroupClass": {
"$type": "Asi.Soa.Membership.DataContracts.GroupClassSummaryData, Asi.Contracts",
"GroupClassId": "RELATIONSHIP",
"Name": "Relationship",
"Description": "",
"IsRelationshipGroup": true
},
"IsRelationshipGroup": true
},
"Party": {
"$type": "Asi.Soa.Membership.DataContracts.PartySummaryData, Asi.Contracts",
"CityName": "Holland",
"CountryName": "United States",
"CountrySubEntityName": "MI",
"Email": "",
"Phone": "(616) 399-2220",
"PartyId": "2519",
"Id": "2519",
"UniformId": "7f6e7fb6-5585-459f-a812-2aa92fd7a3b4",
"Status": {
"$type": "Asi.Soa.Membership.DataContracts.PartyStatusData, Asi.Contracts",
"PartyStatusId": "A",
"Name": "Active",
"Description": "Active"
},
"Name": "National Bulk Equipment, Inc.",
"Sort": "NATIONAL BULK EQUIPMENT, INC.",
"IsMarkedForDelete": false
},
"IsActive": false
}
LegacyBIlling endpoint Parameters
Hello I am trying to run some individual rebills through the api, and I've read this post, https://developer.imis.com/discuss/608f556d40271e0038e8bb3c as well as a few others that are related. However I cant seem to get the parameters correct, and I keep getting a 400 bad request with the following body,
Passwordless Connections
Our members struggle mightily with remembering usernames and passwords. Is ASI giving thought to something like passwordless connections, https://auth0.com/docs/authenticate/passwordless, for end users.
Updating a Specific Activity Record Error
Hello,
Making async calls from an iPart
We have some custom .ascx iParts four our on-prem iMIS 20.2.65.9449 version, to which we applied the Telerik security update from march 2020 (Telerik version is 2020.1.219.45).
We are now trying to update the iParts to make some post async calls to a web API for integration with other systems (we need to send some notification messages about custom data used by the iParts).
The iParts use target .NET framework 4.6.2 (as per current version of iMIS) and System.Net.http runtime 4.1.1.3.
We followed recommended practices for making the async calls.