cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Testing Custom Connector gives error 500 ( "message": "Unable to connect to the remote server", "source": "europe-002.azure-apim.net",)

Good Day,

 

I have created a custom connector from a swagger json file.

 

When testing I get this error. See screenshot.

Can anyone help me or point me in the right direction to fix this.

Appreciate an help. 

Many thanks

 

CustomAPICapture.JPG

 

 

4 REPLIES 4
rogersonra
Frequent Visitor

How are you creating the custom connector?  If it is being created from a swagger file can you post the swagger?

 

rogersonra

Hi @rogersonra ,

 

Many thanks for taking time to reply. The Denodo software (middleware) created the swagger json file. I then created the custom connector from it. Here it is:

 

swagger: '2.0'
info: {description: 'This web service provides operations on these Virtual DataPort
views:

* "ccpb_main"."dv_google_employee_details"


*Additional information about Denodo Web Services can be found in [the documentation](https://community.denodo.com/docs/html/browse/7.0/vdp/administration/restful_architecture/restful_we...',
version: 1.0.0, title: restapi_google_employee_details}
host: 192.168.135.60:9090
basePath: /server/ccpb_reporting/restapi_google_employee_details
schemes: [http]
consumes: []
produces: []
paths:
/views/dv_google_employee_details/$xsd:
get:
tags: [dv_google_employee_details]
description: Returns the XSD describing the output of view dv_google_employee_details.
It contains the published fields and types of the view. The names of the fields
are as they appear in the web service, not in the view (they may have been
renamed in the web service's configuration)
operationId: xsd_dv_google_employee_details
produces: [application/xml; charset=UTF-8; subtype=denodo-7.0]
parameters:
- {$ref: '#/parameters/user_agent_header_parameter'}
responses:
'200':
description: Success
schema: {$ref: '#/definitions/dv_google_employee_details_xsd_def'}
'400': {description: Bad request}
'401': {description: Authentication failed}
'403': {description: Insufficient permissions to perform this request}
'500': {description: Runtime error}
/views/dv_google_employee_details/$count:
get:
tags: [dv_google_employee_details]
description: Returns the number of rows returned by a query to view dv_google_employee_details
operationId: count_dv_google_employee_details
produces: [text/html; charset=UTF-8; subtype=denodo-7.0, text/plain]
parameters:
- {$ref: '#/parameters/count_parameter'}
- {$ref: '#/parameters/display_restful_references_parameter'}
- {$ref: '#/parameters/expand_parameter'}
- {$ref: '#/parameters/filter_parameter'}
- {$ref: '#/parameters/format_parameter'}
- {$ref: '#/parameters/group_by_parameter'}
- {$ref: '#/parameters/having_parameter'}
- {$ref: '#/parameters/jsoncallback_parameter'}
- {$ref: '#/parameters/noescape_html_parameter'}
- {$ref: '#/parameters/order_by_parameter'}
- {$ref: '#/parameters/select_parameter'}
- {$ref: '#/parameters/start_index_parameter'}
- {$ref: '#/parameters/user_agent_header_parameter'}
responses:
'200':
description: Success
schema: {type: integer, format: int64}
'204': {description: No results were returned}
'400': {description: Bad request}
'401': {description: Authentication failed}
'403': {description: Insufficient permissions to perform this request}
'500': {description: Runtime error}
/views/dv_google_employee_details:
get:
tags: [dv_google_employee_details]
description: Returns values of view dv_google_employee_details
operationId: queryView_dv_google_employee_details
produces: [application/json; charset=UTF-8; subtype=denodo-7.0, text/html; charset=UTF-8;
subtype=denodo-7.0, application/xml; charset=UTF-8; subtype=denodo-7.0]
parameters:
- {$ref: '#/parameters/count_parameter'}
- {$ref: '#/parameters/display_restful_references_parameter'}
- {$ref: '#/parameters/expand_parameter'}
- {$ref: '#/parameters/filter_parameter'}
- {$ref: '#/parameters/format_parameter'}
- {$ref: '#/parameters/group_by_parameter'}
- {$ref: '#/parameters/having_parameter'}
- {$ref: '#/parameters/jsoncallback_parameter'}
- {$ref: '#/parameters/noescape_html_parameter'}
- {$ref: '#/parameters/order_by_parameter'}
- {$ref: '#/parameters/select_parameter'}
- {$ref: '#/parameters/start_index_parameter'}
- {$ref: '#/parameters/user_agent_header_parameter'}
responses:
'200':
description: Success
schema: {$ref: '#/definitions/dv_google_employee_details_response_def'}
'204': {description: No results were returned}
'400': {description: Bad request}
'401': {description: Authentication failed}
'403': {description: Insufficient permissions to perform this request}
'500': {description: Runtime error}
post:
tags: [dv_google_employee_details]
description: Inserts a new row on view dv_google_employee_details
operationId: insertResource_dv_google_employee_details
consumes: [application/json, application/xml]
produces: [application/json, application/xml]
parameters:
- {$ref: '#/parameters/user_agent_header_parameter'}
- in: body
name: New element
required: false
schema: {$ref: '#/definitions/dv_google_employee_details_element_post_def'}
responses:
'201': {description: Success}
'400': {description: Bad request}
'401': {description: Authentication failed}
'403': {description: Insufficient permissions to perform this request}
'500': {description: Runtime error}
/views/dv_google_employee_details/$metadata:
get:
tags: [dv_google_employee_details]
description: Returns the metadata of view dv_google_employee_details. This includes
the description of the view and the URLs to retrieve its schema and its associations.
operationId: metadata_dv_google_employee_details
produces: [application/json; charset=UTF-8; subtype=denodo-7.0, application/xml;
charset=UTF-8; subtype=denodo-7.0]
parameters:
- {$ref: '#/parameters/reduced_format_parameter'}
- {$ref: '#/parameters/user_agent_header_parameter'}
responses:
'200':
description: Success
schema: {$ref: '#/definitions/dv_google_employee_details_metadata_def'}
'400': {description: Bad request}
'401': {description: Authentication failed}
'403': {description: Insufficient permissions to perform this request}
'500': {description: Runtime error}
/views/dv_google_employee_details/$schema:
get:
tags: [dv_google_employee_details]
description: Returns the schema of view dv_google_employee_details. This a list
of the published fields and types of the view. The names of the fields are
as they appear in the web service, not in the view (they may have been renamed
in the web service's configuration)
operationId: schema_dv_google_employee_details
produces: [application/json; charset=UTF-8; subtype=denodo-7.0, application/xml;
charset=UTF-8; subtype=denodo-7.0]
parameters:
- {$ref: '#/parameters/user_agent_header_parameter'}
responses:
'200':
description: Success
schema: {$ref: '#/definitions/dv_google_employee_details_schema_def'}
'400': {description: Bad request}
'401': {description: Authentication failed}
'403': {description: Insufficient permissions to perform this request}
'500': {description: Runtime error}
/views/dv_google_employee_details/$associations:
get:
tags: [dv_google_employee_details]
description: Returns the metadata of the associations related to view dv_google_employee_details
that are published with the service
operationId: associations_dv_google_employee_detailsdv_google_employee_details
produces: [application/json; charset=UTF-8; subtype=denodo-7.0, application/xml;
charset=UTF-8; subtype=denodo-7.0]
parameters:
- {$ref: '#/parameters/reduced_format_parameter'}
- {$ref: '#/parameters/user_agent_header_parameter'}
responses:
'200':
description: Success
schema: {$ref: '#/definitions/associations_def'}
'400': {description: Bad request}
'401': {description: Authentication failed}
'403': {description: Insufficient permissions to perform this request}
'500': {description: Runtime error}
definitions:
links_def:
required: [href, rel]
properties:
rel:
type: string
xml: {attribute: true}
href:
type: string
xml: {attribute: true}
title:
type: string
xml: {attribute: true}
type:
type: string
xml: {attribute: true}
description: MIME type of a blob
xml: {name: link, namespace: 'http://www.w3.org/2005/Atom'}
associations_def:
properties:
view-name:
type: string
xml: {attribute: true}
description: Virtual DataPort view name
association-metadata:
type: string
items:
type: object
properties:
endpoints:
type: string
items:
type: object
xml: {name: endpoint}
properties:
multiplicity:
type: string
xml: {attribute: true}
description: Multiplicity at this end point
enum: ['0,1', '1', '0,*', +]
principal:
type: boolean
xml: {attribute: true}
description: Whether this end point is principal or dependent
role-description:
type: string
xml: {attribute: true}
description: Role description
role-name:
type: string
xml: {attribute: true}
description: Role name at this endpoint
view-name:
type: string
xml: {attribute: true}
description: Virtual DataPort view name at this end point
link: {$ref: '#/definitions/links_def'}
name:
type: string
xml: {attribute: true}
description: Association name
referential-constraint:
type: boolean
xml: {attribute: true}
description: Whether this association defines a referential constraint
or not
link: {$ref: '#/definitions/links_def'}
xml: {name: view-associations, namespace: 'http://www.denodo.com/restful'}
dv_google_employee_details_element_def:
properties:
employee_number: {type: integer, format: int32, description: 'Virtual DataPort
type: int'}
surname: {type: string, description: 'Virtual DataPort type: text'}
first_name: {type: string, description: 'Virtual DataPort type: text'}
centre_code: {type: string, description: 'Virtual DataPort type: text'}
centre_name: {type: string, description: 'Virtual DataPort type: text'}
department_code: {type: string, description: 'Virtual DataPort type: text'}
department_name: {type: string, description: 'Virtual DataPort type: text'}
personnelareatext_0: {type: string, description: 'Virtual DataPort type: text'}
plant_code: {type: string, description: 'Virtual DataPort type: text'}
plant: {type: string, description: 'Virtual DataPort type: text'}
links:
type: array
items: {$ref: '#/definitions/links_def'}
description: Extended schema of view dv_google_employee_details
xml: {name: dv_google_employee_details, namespace: 'http://www.denodo.com/restful/ccpb_main/views/dv_google_employee_details'}
dv_google_employee_details_element_post_def:
properties:
employee_number: {type: integer, format: int32, description: 'Virtual DataPort
type: int'}
surname: {type: string, description: 'Virtual DataPort type: text'}
first_name: {type: string, description: 'Virtual DataPort type: text'}
centre_code: {type: string, description: 'Virtual DataPort type: text'}
centre_name: {type: string, description: 'Virtual DataPort type: text'}
department_code: {type: string, description: 'Virtual DataPort type: text'}
department_name: {type: string, description: 'Virtual DataPort type: text'}
personnelareatext_0: {type: string, description: 'Virtual DataPort type: text'}
plant_code: {type: string, description: 'Virtual DataPort type: text'}
plant: {type: string, description: 'Virtual DataPort type: text'}
description: Schema of view dv_google_employee_details as required by POST requests
xml: {name: dv_google_employee_details, namespace: 'http://www.denodo.com/restful/ccpb_main/views/dv_google_employee_details'}
dv_google_employee_details_element_put_def:
properties:
employee_number: {type: integer, format: int32, description: 'Virtual DataPort
type: int'}
surname: {type: string, description: 'Virtual DataPort type: text'}
first_name: {type: string, description: 'Virtual DataPort type: text'}
centre_code: {type: string, description: 'Virtual DataPort type: text'}
centre_name: {type: string, description: 'Virtual DataPort type: text'}
department_code: {type: string, description: 'Virtual DataPort type: text'}
department_name: {type: string, description: 'Virtual DataPort type: text'}
personnelareatext_0: {type: string, description: 'Virtual DataPort type: text'}
plant_code: {type: string, description: 'Virtual DataPort type: text'}
plant: {type: string, description: 'Virtual DataPort type: text'}
description: Schema of view dv_google_employee_details as required by PUT requests
xml: {name: dv_google_employee_details, namespace: 'http://www.denodo.com/restful/ccpb_main/views/dv_google_employee_details'}
dv_google_employee_details_element_simplified_def:
properties:
employee_number:
type: object
properties:
type: {type: string, description: The type of the field}
surname:
type: object
properties:
type: {type: string, description: The type of the field}
first_name:
type: object
properties:
type: {type: string, description: The type of the field}
centre_code:
type: object
properties:
type: {type: string, description: The type of the field}
centre_name:
type: object
properties:
type: {type: string, description: The type of the field}
department_code:
type: object
properties:
type: {type: string, description: The type of the field}
department_name:
type: object
properties:
type: {type: string, description: The type of the field}
personnelareatext_0:
type: object
properties:
type: {type: string, description: The type of the field}
plant_code:
type: object
properties:
type: {type: string, description: The type of the field}
plant:
type: object
properties:
type: {type: string, description: The type of the field}
description: Schema of view dv_google_employee_details
xml: {name: dv_google_employee_details, namespace: 'http://www.denodo.com/restful/ccpb_main/views/dv_google_employee_details'}
dv_google_employee_details_xsd_def:
properties:
targetNamespace:
type: string
xml: {attribute: true}
description: 'Namespace defined by this XSD: http://www.denodo.com/restful/ccpb_main/views/dv_google_employee_details'
element:
type: object
properties:
complexType:
type: object
properties:
sequence:
type: object
properties:
centre_code:
type: object
xml: {name: element}
properties:
name:
type: string
xml: {attribute: true}
type:
type: string
xml: {attribute: true}
description: 'Virtual DataPort type: text'
nillable:
type: boolean
xml: {attribute: true}
centre_name:
type: object
xml: {name: element}
properties:
name:
type: string
xml: {attribute: true}
type:
type: string
xml: {attribute: true}
description: 'Virtual DataPort type: text'
nillable:
type: boolean
xml: {attribute: true}
department_code:
type: object
xml: {name: element}
properties:
name:
type: string
xml: {attribute: true}
type:
type: string
xml: {attribute: true}
description: 'Virtual DataPort type: text'
nillable:
type: boolean
xml: {attribute: true}
department_name:
type: object
xml: {name: element}
properties:
name:
type: string
xml: {attribute: true}
type:
type: string
xml: {attribute: true}
description: 'Virtual DataPort type: text'
nillable:
type: boolean
xml: {attribute: true}
employee_number:
type: object
xml: {name: element}
properties:
name:
type: string
xml: {attribute: true}
type:
type: string
xml: {attribute: true}
description: 'Virtual DataPort type: int'
nillable:
type: boolean
xml: {attribute: true}
first_name:
type: object
xml: {name: element}
properties:
name:
type: string
xml: {attribute: true}
type:
type: string
xml: {attribute: true}
description: 'Virtual DataPort type: text'
nillable:
type: boolean
xml: {attribute: true}
personnelareatext_0:
type: object
xml: {name: element}
properties:
name:
type: string
xml: {attribute: true}
type:
type: string
xml: {attribute: true}
description: 'Virtual DataPort type: text'
nillable:
type: boolean
xml: {attribute: true}
plant:
type: object
xml: {name: element}
properties:
name:
type: string
xml: {attribute: true}
type:
type: string
xml: {attribute: true}
description: 'Virtual DataPort type: text'
nillable:
type: boolean
xml: {attribute: true}
plant_code:
type: object
xml: {name: element}
properties:
name:
type: string
xml: {attribute: true}
type:
type: string
xml: {attribute: true}
description: 'Virtual DataPort type: text'
nillable:
type: boolean
xml: {attribute: true}
surname:
type: object
xml: {name: element}
properties:
name:
type: string
xml: {attribute: true}
type:
type: string
xml: {attribute: true}
description: 'Virtual DataPort type: text'
nillable:
type: boolean
xml: {attribute: true}
name:
type: string
xml: {attribute: true}
description: 'Names of the view: dv_google_employee_details'
description: Schema of view dv_google_employee_details in XSD format
xml: {name: schema, namespace: 'http://www.w3.org/2001/XMLSchema'}
dv_google_employee_details_response_def:
properties:
name:
type: string
xml: {attribute: true}
description: Virtual DataPort view name
description:
type: string
xml: {attribute: true}
description: Virtual DataPort view description
elements:
type: string
description: Results returned by the query
items: {$ref: '#/definitions/dv_google_employee_details_element_def'}
links:
type: string
description: Links available for the current element (e.g. pagination links)
items: {$ref: '#/definitions/links_def'}
xml: {name: view, namespace: 'http://www.denodo.com/restful'}
dv_google_employee_details_schema_def:
properties:
name: {type: string, description: Virtual DataPort view name}
properties: {$ref: '#/definitions/dv_google_employee_details_element_simplified_def'}
dv_google_employee_details_metadata_def:
properties:
name:
type: string
xml: {attribute: true}
description: Virtual DataPort database name
description:
type: string
xml: {attribute: true}
description: Virtual DataPort database description
views-metadata:
type: object
xml: {name: view-metadata}
properties:
links:
type: string
items: {$ref: '#/definitions/links_def'}
name:
type: string
xml: {attribute: true}
description: Virtual DataPort view name
required: [links, name]
xml: {name: db, namespace: 'http://www.denodo.com/restful'}
parameters:
count_parameter: {name: $count, in: query, description: Used for pagination in view
resources, required: false, type: integer}
select_parameter:
name: $select
in: query
description: Comma-separated list of fields to be returned in the result
required: false
type: string
items: {type: string}
collectionFormat: csv
start_index_parameter: {name: $start_index, in: query, description: Used for pagination
in view resources, required: false, type: integer}
noescape_html_parameter:
name: $noescapehtml
in: query
description: List of comma-separated fields whose values will not be HTML escaped.
required: false
type: string
items: {type: string}
collectionFormat: csv
user_agent_header_parameter: {name: user-agent, in: header, description: 'By including
this header, communication between the web service and the Virtual DataPort
will be configured with this value.', required: false, type: string}
filter_parameter: {name: $filter, in: query, description: Filters the rows of a
view using any condition. Any expression that can appear in the WHERE clause
of a VQL query can be used., required: false, type: string}
jsoncallback_parameter: {name: $jsoncallback, in: query, description: 'The JSON
representation can return the data of a view prefixed with the name of a function.
This is called JSON with padding or JSONP. That way, when a browser receives
the response, it receives a script rather than data.', required: false, type: string}
reduced_format_parameter:
name: $format
in: query
description: Defines the output format of the query
required: false
type: string
default: XML
enum: [JSON, XML]
having_parameter:
name: $having
in: query
description: Comma-separated list of fields to add to the HAVING clause of the
query
required: false
type: string
items: {type: string}
collectionFormat: csv
display_restful_references_parameter: {name: $displayRESTfulReferences, in: query,
description: 'By default, the result of requesting a view contains, in each row,
a link to the row itself and, for each association of the view, a link to traverse
the association. By using this parameter, you can configure this behavior.',
required: false, type: boolean}
expand_parameter:
name: $expand
in: query
description: Roles to expand in the query
required: false
type: string
items: {type: string}
collectionFormat: csv
order_by_parameter:
name: $orderby
in: query
description: Sorts the results by one or more fields. It is a comma-separated
list of fields, each one followed by the modifier ASC (for ascending order)
and DESC (for descending order).
required: false
type: string
items: {type: string}
collectionFormat: csv
format_parameter:
name: $format
in: query
description: Defines the output format of the query
required: false
type: string
default: JSON
enum: [JSON, HTML, XML]
group_by_parameter:
name: $groupby
in: query
description: Comma-separated list of fields to group by with
required: false
type: string
items: {type: string}
collectionFormat: csv
responses: {}
securityDefinitions:
basic_auth: {type: basic}
security:
- basic_auth: []
tags:
- {name: dv_google_employee_details, description: Operations available for view dv_google_employee_details}

Hi @fransk

I had a similar issue issue a while ago and adding

summary: <some summary text>

to each operationId solved the problem for me.

So I would have something like

paths:
  /students/{id}:
    get:
      summary: Get by id
      description: Get by id
      operationId: GetByID
 
Hopefully it's as simple as this.  Other than that it's beyond me but hopefully this will help.
 
rogersonra

Thanks for the reply @rogersonra 

 

Will have a look into it.

 

Regards

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages