Krzysztof Bialowas (aka KB)

Saturday fun 😀

For sure not new. For sure not super advanced but problem is... bot everyone follow them. That is the biggest problem. Sometimes I have fealing we forgetting those basics

GitHub - mynavblog/ALForMoreAdvancedDevelopers: Business Central Workbook for more advanced developers Business Central Workbook for more advanced developers - mynavblog/ALForMoreAdvancedDevelopers

I would like to introduce a new workbook for more advanced developers #MSDyn365BC. This time about:

✅ Interfaces
✅ Queries & APIs
✅ Lists, Dictionaries, and more!

📚 It's free! Use it, share it, and grow.

github.com/mynavblog/AL...

Plus:
6. Add auto-merge when all done
7. Delete branches when merged
and in the past already added:
8. Check spelling
9. Check TODOs in code

Playing around with Github PRs for #MSDyn365BC apps can be additive. So for last days:
1. Add labels based on folder that has been changed
2. Add labels based on size
3. Blocked wrongly named PRs
4. Blocked if PR does not been approved to release
5. Add automatic reviewers

Labeler - GitHub Marketplace Automatically label new pull requests based on the paths of files being changed

This is almost out of the box. Check Github Action github.com/marketplace/... . The size of the PR I am using the 2nd action: github.com/marketplace/... If you need some help let me know I can help with more screenshots

And another one to make a #MSDyn365BC apps build even easier in Github. The pull request name must be started with one of the below prefixes if not reject 😜

Finally had some moment to play around with Github Actions in our #MSDyn365BC product repository. Now the labels are assigned automatically based on size of the pull request and the extension that we are modifying

I think for AppSource apps minimum should be AllowDebugging to allow any customer/partner found the issues. For PTE apps it always should be in my opinion allowed to download source since customer should be able to change the partner when wants and be able fix issues in any case. That my view.

I dont think so. However for me interesting is why would you like to do that?

3. They could add button to show the detailed errors for better UI but then how to show them. You anyway will end up with what I showed you above.

1. AddAction - not always works, we have seen number of cases where action cannot be added. Maybe this is one of them (there is no error in code)
2. Good 😂
3. When you collect errors you have to use page to show them. Otherwise you see such error message as you have.

Not exactly :) in this you need to show collected errors later. But you are right you cannot show the Action when you collecting the errors. For that you need to use Recommended Actions in the Error Message Page.

GitHub - mynavblog/ALForMoreAdvancedDevelopers: Business Central Workbook for more advanced developers Business Central Workbook for more advanced developers - mynavblog/ALForMoreAdvancedDevelopers

Check the chapter about errors in my workbook. Hope it will help since I trued to explain that there github.com/mynavblog/AL...

Is this standard code or your/partner code?

In such case you will find details when you copy the error to clipboard and paste it in the notepad.

Being a #MSDyn365BC consultant is fun. Status of last 13h: 4 meetings, 3 with Australian Customers and 1 with New Zeleand. And it is 9 AM Local time 😂

Good question. I am working with sharepoint since has less limitations. But for one customer I want to start OneDrive for now does not look promising but we will see

In this case I am service manager who got some service commitments

Then I would also escalate that: Adding things to all RC also is not great idea - and moreover duplicate cues that are standard does not make sense. Also if I see Revenue Current Month 0 having sales this month in other cue with high number looks odd.

Not exactly 😀 You would need to change to Premium BC.

Small trivia about #msdyn365bc. Which from the below are related to Service Contracts and which one is not. 🤔