Resource not found for the segment issue in Power Automate/Microsoft Flow


Please refer below post for fixing this issue with your power automate flow.

Original post by: nagaraja2026Advocate IV

image.png

Recently , I have come across this issue with Power Automate while I am trying to create a record using “Create a new record ” action with Common Data Service(Current environment) connector based on some trigger.

I am not doing any complex stuff, just creating a quote line record and referencing a quote record. Referencing records is as simple as using dynamic content and populating it to a lookup attribute right !!! No, its not. Let’s see.

image.png

I just run the flow with the above setup and flow run got failed with “Resource not found for the segment ‘c262238e-fc89-ea12-ba11-000d3ab615df’”

image.png

After some digging , found the cause. The new CDS ( Current environment) is the culprit. Issue is with the way of referencing attributes .It expects referenced attribute values in “Odata Id” format i.e

EntityNameInPlural(Record’sId/GUID).

So here in my case, for quote lookup attribute I should give like /quotes/(Record’s Id/GUID).

image.png

After making the above change, flow has run successfully.

The interesting thing is If you use old CDS connector, you wont face this issue. But we cannot be compromised to use old one cause the new connector gives us lot of advantages. Like, option to configure multiple trigger . Read here.

If you want to know the difference between CDS vs CDS (Current environment) connectors, refer this excellent article by Sara Lagerquist (MVP)

Hope it helps. Original post is from my blog.

Future of developers in Power Platform

Dreaming in CRM & Power Platform

Generally all my posts are problem-solution type posts. I never write anything that is purely my opinion. But, considering the recent developments, I thought I should sit down and write down my thoughts. Before we even consider whether developers have a future in Power Platform, we need to first delve into the historical context of the developer’s role and their tasks in Dynamics CRM.

In the beginning of time

I come from a technical background, starting with ASP.NET WebForms, C# and Dynamics CRM OnPremise. Back in those days my role mostly revolved around Plugin, custom workflow assemblies, a bit of JavaScript to do data validation, hiding/unhiding or enabling/disabling fields. I also occasionally had to use Deployment Manager to do some backup/restore or UR installations.

A CRM Developer had to just know C#, CRM SDK, understand a bit of JavaScript to write crmForm.all. You never had to be highly skilled in…

View original post 2,230 more words

Error Fix in Creating Dynamics 365 Trial

Srinath Pega

Creating Dynamics 365 trial https://trials.dynamics.com/ , Its asking business identity means need a business domain.

Learn More on Domain : https://docs.microsoft.com/en-gb/microsoft-365/admin/get-help-with-domains/what-is-a-domain

Creating Dynamics 365 Trail from Power Apps:

  1. Go to https://powerapps.microsoft.com/en-us/

2. Click on pricing on navigation . It will open below screen.

3. Click on Try free. Opens the Power Apps Trial Instance creation screen.

4. Enter Mail ID and Click on Next.

5. Click on Set Up Account.

6. It will asks some basic information. fill the details and click Next.

7. Verify the mobile number.

8. Enter the Business name and Check Availability.

9. Checking the Business Name, Click on Next.

10. Enter the Business Identity information. and Click on Sign Up.

11. Click on Go to SetUp .

12. It navigates to Microsoft 365 admin center – Home .

13. Now Open https://trials.dynamics.com/ to create Dynamics 365 Trial Instance.

14. Click on

View original post 74 more words

Role of Tester (QA) in Modern Delivery Models of SDLC

Role of Tester in Modern Delivery

Considering the many advantages of having a separate testing/QA team, we must be having tester/QA in the team for modern delivery process.

Testers should be responsible for following items:

  1. Review Functional Design
  2. Writing Test Cases
  3. Support developers in unit testing
  4. Testing the Features in Dev Instances
  5. Creating Test Automation Script
  6. Exploratory Testing in SIT
  7. Supporting UAT testers in UAT

Testing Activities in Modern Delivery

Testers should do following activities during the various stages of Modern Delivery.

During Sprint Planning

  1. In sprint planning, a tester should help in picking a user-story from the product backlog for development, Design Review & Test case creation.
  2. As a tester, he/she should decide how many hours (Effort Estimation) it should take to finish testing for each of selected user stories for development.
  3. As a tester, he/she should decide how many hours (Effort Estimation) it should take to finish Functional Design Review and Test Case creation for each of selected user stories for Test Case Creation.
  4. As a tester, he/she should decide how many hours (Effort Estimation) it should take support UAT team.
  5. As a tester, he/she must know what sprint goals are.
  6. As a tester, contribute to the prioritizing process.

During Sprint

  1. Review Design and Write Test Cases for User Stories selected for creating Test Cases.
  2. Create Query Clarification Work Item for any design related query.
  3. Support developers in unit testing.
  4. Test user-story in Dev instance when completed. Manual Test execution will be performed in an instance where both tester and developer will work hand in hand.
  5. Tester will be responsible for developing automation scripts.
  6. Perform exploratory testing for all the work items deployed to SIT instance.
  7. Defects will be logged in Defect Management tool which will be tracked daily. Defects will be conferred and analyzed during the Triage call. Defects will be retested as soon as it is resolved and deployed for testing.
  8. Send Test Reports to the stakeholders.
  9. As a tester, he/she attends all daily standup meeting to speak up.
  10. As a tester, he/ she can bring any backlog item that cannot be completed in the current sprint and put to the next sprint.
  11. Support for UAT team.
  12. Executing non-functional testing for approved user stories.

During Sprint Retrospective

  1. As a tester, he/she will figure out what went wrong and what went right in the current sprint.
  2. As a tester, he/she identifies lesson learned and best practices.

QA challenges with agile software development

Agile Testing

Agile Testing is a testing practice that follows the rules and principles of agile software development. Unlike the Waterfall method, Agile Testing can begin at the start of the project with continuous integration between development and testing. Agile Testing methodology is not sequential but continuous.

QA challenges

a) Chances of error are more in agile, as documentation is given less priority, eventually puts more pressure on QA team

b) New features are introduced quickly, which reduces the available time for test teams to identify whether the latest features are according to the requirement and does it truly address the business suits

c) Testers are often required to play a semi-developer roled

d) Test execution cycles are highly compressed

e) Very less time to prepare test plan

f) For regression testing, they will have minimal timing

g) Change in their role from being a gate-keeper of quality to being a partner in Quality

h) Requirement changes and updates are inherent in an agile method, becoming the biggest challenge for QA

Risks

  • Automated UI provides a high level of confidence, but they are slow to execute, fragile to maintain and expensive to build. Automation may not significantly improve test productivity unless the testers know how to test
  • Unreliable tests are a major concern in automated testing. Fixing failing tests and resolving issues related to brittle tests should be a top priority in order to avoid false positives
  • If the automated test are initiated manually rather than through CI (Continuous Integration) then there is a risk that they are not regularly running and therefore may cause failing of tests
  • Automated tests are not a replacement for an exploratory manual testing. To obtain the expected quality of the product, a mixture of testing types and levels is required
  • Many commercially available automation tools provide simple features like automating the capture and replay of manual test cases. Such tool encourages testing through the UI and leads to an inherently brittle and difficult to maintain tests. Also, storing test cases outside the version control system creates unnecessary complexity
  • In order to save time, much times the automation test plan is poorly planned or unplanned which results in the test fail
  • A test set up and tear down procedures are usually missed out during test automation, while Performing manual testing, a test set up and tear down procedures sounds seamless
  • Productivity metrics such as a number of test cases created or executed per day can be terribly misleading, and could lead to making a large investment in running useless tests
  • Members of the agile automation team must be effective consultants: approachable, cooperative, and resourceful, or this system will quickly fail
  • Automation may propose and deliver testing solutions that require too much ongoing maintenance relative to the value provided
  • Automated testing may lack the expertise to conceive and deliver effective solutions
  • Automated testing may be so successful that they run out of important problems to solve, and thus turn to unimportant problems.

Conclusion

Agile methodology in software testing involves testing as early as possible in the software development lifecycle. It demands high customer involvement and testing code as soon as it becomes available. The code should be stable enough to take it to system testing. Extensive regression testing can be done to make sure that the bugs are fixed and tested. Mainly, Communication between the teams makes agile model testing success!!!

How to create Microsoft Dynamics 365 Trial instance?

Arun Potti's MS CRM blog

Follow the below steps to create Dynamics 365 Trial instance in a New User interface.

Step 1: Browse the link https://trials.dynamics.com

Step 2: Click on Sign up here.

Step 3: Click on No, continue signing up.

Step 4: Once the below web page is displayed, provide your Work or Personal Email Id. Click on Next.

Step 5: Click on Set up account.

Step 6: Provide your personal information and click on Next.

Step 7: Choose your Country Code and Provide your Phone number for OTP verification.

You can choose either Text me or Call me.

Click on Send Verification Code.

Note:

If you choose Text me, you will get a SMS. Other wise, if you choose Call me you will get a call from Microsoft and Verification code will be informed over the call.

Step 8: Provide the Verification code received on…

View original post 276 more words

Why do we need Functional/UI Testing if we have good set of Unit Tests?

Reference: Link

If you’ve got a good set of unit tests, do you even need to do functional testing through the UI? Experienced testers are probably doing a spit-take just hearing the question, but, believe it or not,  I’ve heard that question recently from a few different people, and I think the question reflects the excitement they have for the benefits of unit testing. There’s no doubt, unit tests have finally brought testing to the front-line of development, and they’ve improved the quality of countless projects. But, do unit tests make other tests unnecessary? Not by a long shot, you’ll need more than unit tests for a professional quality application. Here are a few reasons why:

Who’s Watching the Watchmen?

Developers are supposed to write their own unit tests to test the code they write. It’s a great rule for writing and refactoring code, but it’s a bad rule for thorough testing. It’s too easy to write the tests with the same mindset used to write the code, and consequently, miss the same problems. Thorough testing requires another set of eyes to fully exercise code without the same prejudices and assumptions as the person who created it.

Unit Tests Don’t Test The UI

Most application users spend all of their time interacting with your program through it’s UI, it’s user interface. Unit tests are back-end tests, they can check that a calculation is correct, but they can’t verify that the results display correctly to your user. And what about problems like unreadable color combinations, incorrect icons, or missing or mislabeled fields? You need UI testing to catch those problems. Or, what if the unit tests work perfectly, but someone ignored your clean model-view-controller architecture, just this once, and slipped a quick calculation fix into your display code? Also, what is your code is missed during deployment? It happens, and when it does, a UI test is the best way to find errors in it before your users do.

Unit Tests Don’t Like Black-Box Apps

Many companies have mission critical applications that depend on an off-the-shelf component or application without source code. Unit tests need source code to be effective. Once again, UI testing with simulated user actions is needed to work out these black-box applications. Also if your project is using some built in product and has some customization on top of it, programmers will have control only of customization code and will write unit test case for customization only. What if the issue is with the product code itself? What if the product team releases a patch making the customization code incompatible? It happens, and when it does, a UI test is the best way to find errors in it before your users do.

Unit Tests Are For Methods, Not Systems

Finally, unit tests are meant to be small, fast, encapsulated tools to test classes and methods in isolation. They don’t test what happens to your application under real-world conditions. How does your app behave under difference version of OS or web browsers? What happens to your server when 30 or 300 users access it simultaneously? How about the same test with 5 years of data on 40,000 accounts? You know the answer, functional testing via the user interface is usually the fastest and most effective way to broaden the scope and depth of your testing to include real-world scenarios which integrate all the components of your application system.

Seriously…

Unit tests are fantastic, but development and QA teams need all the tools they can get to catch defects before software is released. Automated UI testing should be a standard part of your team’s tool set if you’re serious about software quality.

Suggest Tests to ensure quality

Unit Tests, Automated Integration Tests, Automated Functional and UI Tests and finally Manual exploratory tests and Bug bash is needed to ensure quality.

Microsoft Power Platform: 2020 release wave 2 plan

Reference: Link

Download the 2020 release wave 2 PDF (last updated July 8, 2020).

The Microsoft Power Platform release plan for the 2020 release wave 2 describes all new features releasing from October 2020 through March 2021 for Power BI, Power Apps, Power Automate, AI Builder, Power Virtual Agents, and Common Data Model and data integration.

2020 release wave 2 overview

Microsoft Power Platform enables users and organizations to analyze, act, and automate on the data to digitally transform their businesses. Microsoft Power Platform today comprises four products: Power BI, Power Apps, Power Automate, and Power Virtual Agents. It also has two add-ons: AI Builder and Power Apps portals.

  • Power BI is investing in three key areas that drive a data culture: amazing data experiences, modern enterprise BI, and insights where decisions are made. Power BI Desktop includes many new capabilities for users to create content quickly and easily, enabling authors to empower their users, enterprise-grade content creation, and AI-infused authoring experiences. Power BI Mobile adds split-view support for iPad. Power BI Service integrates with Azure Synapse to automatically create and manage materialized views on larger Power BI models as well as enhanced integration with SharePoint lists to build additional custom reports. We continue to enhance our data protection capabilities enabling customers to classify and label sensitive data.
  • Power Apps includes significant improvements for Power Apps developers of all skill levels, improving the sophistication and usability of apps that are created across the web and mobile devices. Makers will be able to create Power Apps directly within Microsoft Teams in order to easily customize the Teams experience. Makers will be able to add custom pages to model-driven apps using the app designer, bringing together the best of canvas and model capabilities including custom layouts and components.
    • AI Builder introduces new AI scenarios for receipt scanning and translation, and improvements to connect to remote training data. The AI builder home page and model details page are updated to improve discoverability and integration with Power Apps and Power Automate.
    • Power Apps portals adds Power Virtual Agents as a component in the Power Apps portals Studio, as well as support for code components created using Power Apps component framework.
  • Power Automate will update the offering to combine the best of WinAutomation with the cloud-based AI Builder and connector-based capabilities in automated flows. This new version will offer customers a way to automate everything from Office apps to legacy terminal applications that haven’t been updated in decades. In addition, there are further enhancements coming to automated flows running in the cloud, including richer automation and approval experiences.
  • Power Virtual Agents includes expanded capabilities in the authoring experience, deeper Microsoft Teams integration, tools to create richer content, adaptive cards capabilities, authentication improvements, and improved Power Automate integration.Microsoft Power Platform offers a range of governance and administration capabilities that span Power Apps, Power Automate, and Common Data Service. These capabilities are designed to help the administrators and IT pros in the organization to help set up, secure, manage, govern, and monitor the use and adoption of the platform and its components across the enterprise.
  • Data integration provides built-in connectivity to the Microsoft Power Platform and more, with data across hundreds of business systems, enabling rich and intelligent experiences. There are many new capabilities in this release wave in areas such as dual-write, export to Data Lake, Microsoft Power Platform connectors, Microsoft Power Platform dataflows, Microsoft Power Platform gateway, and Power Query Online.

 Important

The Dynamics 365 features coming in the 2020 release wave 2 have been summarized in a separate release plan.

Key dates for the 2020 release wave 2

This release plan describes functionality that may not have been released yet. Delivery timelines and projected functionality may change or may not ship (see Microsoft policy).

Here are the key dates for the 2020 release wave 2.

MilestoneDateDescription
Release plans availableJuly 8, 2020Learn about the new capabilities coming in the 2020 release wave 2 (October 2020 – March 2021) across Dynamics 365 and the Microsoft Power Platform.
Early access availableAugust 3, 2020Test and validate new features and capabilities that will be a part of the 2020 release wave 2, coming in October, before they get enabled automatically for your end users. You can view the Microsoft Power Platform 2020 release wave 2 early access features now.
General availabilityOctober 1, 2020Production deployment for the 2020 release wave 2 begins. Regional deployments will start on October 2, 2020.

Just like the previous release waves, we continue to call out how each feature will be enabled in your environment:

  • Users, automatically – These features include changes to the user experience for users and are enabled automatically.
  • Admins, makers, or analysts, automatically – These features are meant to be used by administrators, makers, or business analysts and are enabled automatically.
  • Users by admins, makers, or analysts – These features must be enabled or configured by the administrators, makers, or business analysts to be available for their users.

You can get ready with confidence knowing which features will be enabled automatically.

We’ve done this work to help you—our partners, customers, and users—drive the digital transformation of your business on your terms. We’re looking forward to engaging with you as you put these new services and capabilities to work, and we’re eager to hear your feedback as you dig into the 2020 release wave 2.

Let us know your thoughts. Share your feedback on the Microsoft Power Platform community forum. We will use your feedback to make improvements.

Combine Data from Multiple Worksheets Using Power Query

Source: Link Author: Sumit Bansal

When combining data from different sheets using Power Query, it’s required to have the data in an Excel Table (or at least in named ranges). If the data is not in an Excel Table, the method shown here would not work.

Suppose you have four different sheets – East, West, North, and South.

Each of these worksheets has the data in an Excel Table, and the structure of the table is consistent (i.e., the headers are same).

This kind of data is extremely easy to combine using Power Query (which works really well with data in Excel Table).

For this technique to work best, it’s better to have names for your Excel Tables (work without it too, but it’s easier to use when the tables are named).

I have given the tables the following names: East_Data, West_Data, North_Data, and South_Data.

Here are the steps to combine multiple worksheets with Excel Tables using Power Query:

  • Go to the Data tab.
  • In the Get & Transform Data group, click on the ‘Get Data’ option.
  • Go the ‘From Other Sources’ option.
  • Click the ‘Blank Query’ option. This will open the Power Query editor.
  • In the Query editor, type the following formula in the formula bar: =Excel.CurrentWorkbook(). Note that the Power Query formulas are case sensitive, so you need to use the exact formula as mentioned (else you will get an error). 
  • Hit the Enter key. This will show you all the table names in the entire workbook (it will also show you the named ranges and/or connections in case it exists in the workbook).
  • [Optional Step] In this example, I want to combine all the tables. If you want to combine specific Excel Tables only, then you can click the drop-down icon in the name header and select the ones you want to combine. Similarly, if you have named ranges or connections, and you only want to combine tables, you can remove those named ranges as well.
  • In the Content header cell, click on the double pointed arrow.
  • Select the columns that you want to combine. If you want to combine all columns, make sure (Select All Columns) is checked.
  • Uncheck the ‘Use original column name as prefix’ option.
  • Click OK.

The above steps would combine the data from all the worksheets into one single table.

If you look closely, you’ll find the last column (rightmost) has the name of the Excel tables (East_Data, West_Data, North_Data, and South_Data). This is an identifier that tells us which record came from which Excel Table. This is also the reason I said it’s better to have descriptive names for the Excel tables.

Here are a few modifications you can do to the combined data in Power Query itself:

  1. Drag and place the Name column to the beginning.
  2. Remove the “_Data” from the name column (so you’re left with East, West, North, and South in the name column). To do this, right-click on the Name header and click on Replace Values. In the  Replace Values dialog box, replace _Data with a blank.
  3. Change the Data column to show only dates (and not the time). To do this, click the Date column header, go to the ‘Transform’ tab and change the Data type to Date.
  4. Rename the Query to ConsolidatedData.

Now that you have the combined data from all the worksheets in Power Query, you can load it in Excel – as a new table in a new worksheet.

To do this. follow the below steps:

  • Click the ‘File’ tab.
  • Click on Close and Load To.
  • In the Import Data dialog box, select Table and New worksheet options.
  • Click Ok.

The above steps would combine data from all the worksheets and give you that combined data in a new worksheet.

One Issue You Must Resolve when Using This Method

In case you have used the above method to combine all the tables in the workbook, you’re likely to face an issue.

See the number of rows of the combined data – 1304 (which is right).

Now, if I refresh the query, the number of rows changes to 2607. Refresh again and it will change to 3910.

Here is the problem.

Every time you refresh the query, it adds all the records in the original data to the combined data.

Note: You’ll face this issue only if you have used Power Query to combine ALL THE EXCEL TABLES in the workbook. In case you selected specific tables to be combined, you’ll not face this issue.

Let’s understand the cause of this problem and how to correct this.

When you refresh a query, it goes back and follows all the steps that we took to combine the data.

In the step where we used the formula =Excel.CurrentWorkbook(), it gave us a list of all the tables. This worked fine the first time as there were only four tables.

But when you refresh, there are five tables in the workbook – including the new table that Power Query inserted where we have the combined data.

So every time you refresh the query, apart from the four Excel Tables that we want to combine, it also adds the existing query table to the resulting data.

This is called recursion.

Here is how to solve this issue.

Once you insert =Excel.CurrentWorkbook() in the  Power Query formula bar and hit enter, you get a list of Excel Tables. To make sure you only get to combine the tables from the worksheet, you need to somehow filter only these tables that you want to combine and remove everything else.

Here are the steps to make sure you only have the required tables:

  • Click the drop-down and hover the cursor on Text Filters.
  • Click on the Contains option.
  • In the Filter Rows dialog box, enter _Data in the field next to the ‘contains’ option.
  • Click OK.

You may not see any change in the data, but doing this will prevent the resulting table from being added over again when the query is refreshed.

Note that in the above steps we have used “_Data” to filter as we named out tables that way. But what if your tables are not named consistently. What if all the table names are random and have nothing in common.

Here is the way to solve this – use the ‘does not equal’ filter and enter the name of the Query (which would be ConsolidatedData in our example). This will ensure that everything remains the same and the resulting query table which is created is filtered out.

Apart from the fact that Power Query makes this entire process of combining data from different sheets (or even the same sheet) quite easy, another benefit of using it that it makes it dynamic. If you add more records to any of the tables and refresh the Power Query, it will automatically give you the combined data.

Important Note: In the above example, the headers were same. In case the headers are different, Power Query will combine and create all the columns in the new table. If the data is available for that column, it will be shown, else it will show null.

Create your website with WordPress.com
Get started