In desperate need of help build and populating a nested table with 3 levels. When a tech is logged in to a dispatch, they can work on multiple pieces of equipment. Each piece of equipment can have multiple pieces of materials used on it. I need to create a nested table where there is 1 dispatch in the main collection, that collection has a field called TechNotes. Tech notes has 10 columns that needs to hold all of the notes for that 1 dispatch. One of the columns in the TechNotes table is MaterialsUsed. MaterialsUsed has 4 columns and holds all of the materials used on the piece of equipment that is associated with that TechNote item.
I need this in nested tables without HTML so that I can convert it to JSON to send to a flow to fill out a Word Template.
I can't seem to successfully do this....
TRY #1 - Creates a new row at every level (i.e. 3 pieces of material used on 1 piece of equipments & creates 3 lines on each table instead of 1 line on the Dispatch table and 1 line on the TechNotes table and 3 lines on the MaterialsUsed table):
ForAll(Filter('[dbo].[DailySWO_DailyDispatchWorked]', DispatchAssigneeID = SelectedAssigneeID)
, ForAll(Filter('[dbo].[DailySWO_DailyTechNotes]', NoteAssigneeID = DispatchAssigneeID)
, ForAll(Filter('[dbo].[DailySWO_Materials]', MaterialAssigneeID = NoteAssigneeID && MaterialEquipmentID = NoteEquipmentID)
, Collect(CollDispatchSWO, {AssigneeID: DispatchAssigneeID, DisWorkDT: Today(), TechName: User().FullName, DisDispatchNBR: DispatchNumber, AfterhoursID: AfterhoursID,
DisDispatchType: DispatchType, DisSiteNBR: SiteNumber, DisSiteNM: SiteName, DisSiteAddress: SiteAddress, DispatchInfo: DispatchDetails, TorchCB: TorchCB,
VacuumCB: VacuumCB, ReclaimerCB: ReclaimerCB, NitrogenCB: NitrogenCB, TerminalsCB: WireNutsCB, RefrigCapCB: RefrigCapCB, CallSTS: CallSTS, QuoteSTS: QuoteSTS,
CustomerSign: CustSign.Image, CustomerNM: CustSign_CustNM.Text, CustomerEmail: CustSign_CustEmail.Text, SendCustEmail: If(CustSign_CustEmail_YesCB.Value = true, 1, 0),
TechSign: TechSignature.Image, StartTM: TechSign_StartTM.Text, EndTM: TechSign_EndTM.Text, TotalHours: TechSign_TotalHours.Text, PayRate: TechSign_PayRate.Text,
TechNotes: Table({TechNote: TechNote, AreaServed: AreaServed, EquipID: NoteEquipmentID, EquipMake: EquipMake, EquipModel: EquipModel, EquipSerialNBR: SerialNBR,
EquipType: EquipType, UnitNBR: UnitNBR, UnitSTS: UnitSTS, RefrigType: RefrigType, RefrigRemoved: Removed, RefrigAdded: Added,
MaterialsUsed: Table({MatEquipID: MaterialEquipmentID, MatPO: MaterialPO, MatQTY: MaterialQTY, MatDESC: MaterialsDESC})})}))));
TRY #2 - Notes and Materials are in different collections:
ClearCollect(CollDispatchSWO, {AssigneeID: SelectedAssigneeID, DisWorkDT: Today(), TechName: User().FullName, DisDispatchNBR: SelectedDispatchNBR, AfterhoursID: SelectedDispatchOT, DisDispatchType: SelectedDispatchType, DisSiteNBR: SelectedSiteNBR, DisSiteNM: SelectedSiteNM, DisSiteAddress: Concatenate(SelectedSiteStreetAddress, ", ", SelectedSiteCity, ", ", SelectedSiteState, ", ", Text(SelectedSiteZipCD)), DispatchInfo: SelectedDispatchDetails, TorchCB: LookUp('[dbo].[DailySWO_DailyDispatchWorked]', DispatchAssigneeID = SelectedAssigneeID, TorchCB), VacuumCB: LookUp('[dbo].[DailySWO_DailyDispatchWorked]', DispatchAssigneeID = SelectedAssigneeID, VacuumCB), ReclaimerCB: LookUp('[dbo].[DailySWO_DailyDispatchWorked]', DispatchAssigneeID = SelectedAssigneeID, ReclaimerCB), NitrogenCB: LookUp('[dbo].[DailySWO_DailyDispatchWorked]', DispatchAssigneeID = SelectedAssigneeID, NitrogenCB), TerminalsCB: LookUp('[dbo].[DailySWO_DailyDispatchWorked]', DispatchAssigneeID = SelectedAssigneeID, WireNutsCB), RefrigCapCB: LookUp('[dbo].[DailySWO_DailyDispatchWorked]', DispatchAssigneeID = SelectedAssigneeID, RefrigCapCB), CallSTS: LookUp('[dbo].[DailySWO_DailyDispatchWorked]', DispatchAssigneeID = SelectedAssigneeID, CallSTS), QuoteSTS: LookUp('[dbo].[DailySWO_DailyDispatchWorked]', DispatchAssigneeID = SelectedAssigneeID, QuoteSTS), CustomerSign: CustSign.Image, CustomerNM: CustSign_CustNM.Text, CustomerEmail: CustSign_CustEmail.Text, SendCustEmail: If(CustSign_CustEmail_YesCB.Value = true, 1, 0), TechSign: TechSignature.Image, StartTM: TechSign_StartTM.Text, EndTM: TechSign_EndTM.Text, TotalHours: TechSign_TotalHours.Text, PayRate: TechSign_PayRate.Text, TechNotes: Table({TechNote: "", AreaServed: "", EquipID: 0, EquipMake: "", EquipModel: "", EquipSerialNBR: "", EquipType: "", UnitNBR: "", UnitSTS: "", RefrigType: "", RefrigRemoved: "", RefrigAdded: "", MaterialsUsed: Table({MatEquipID: 0, MatPO: "", MatQTY: 0, MatDESC: ""})})});
ForAll(
CollDispatchSWO,
ForAll(Filter('[dbo].[DailySWO_DailyTechNotes]', NoteAssigneeID = SelectedAssigneeID),
Collect(TechNotes,{TechNote: TechNote, AreaServed: AreaServed, EquipID: NoteEquipmentID, EquipMake: EquipMake, EquipModel: EquipModel, EquipSerialNBR: SerialNBR, EquipType: EquipType, UnitNBR: UnitNBR, UnitSTS: UnitSTS, RefrigType: RefrigType, RefrigRemoved: Removed, RefrigAdded: Added, MaterialsUsed: Table({MatEquipID: 0,
MatPO: "", MatQTY: 0, MatDESC: ""})})
)
);
ForAll(
TechNotes,
ForAll(Filter('[dbo].[DailySWO_Materials]', MaterialAssigneeID = SelectedAssigneeID && MaterialEquipmentID = EquipID),
Collect(MaterialsUsed,{MatEquipID: MaterialEquipmentID, MatPO: MaterialPO, MatQTY: MaterialQTY, MatDESC: MaterialsDESC})
)
);
Solved! Go to Solution.
@Anonymous
The following formula will give you the JSON data you are looking for.
With({_data:
ForAll(
Filter('[dbo].[DailySWO_DailyDispatchWorked]',
DispatchAssigneeID = SelectedAssigneeID
) As _disp,
{AssigneeID: _disp.DispatchAssigneeID,
DisWorkDT: Today(),
TechName: User().FullName,
DisDispatchNBR: _disp.DispatchNumber,
AfterhoursID: _disp.AfterhoursID,
DisDispatchType: _disp.DispatchType,
DisSiteNBR: _disp.SiteNumber,
DisSiteNM: _disp.SiteName,
DisSiteAddress: _disp.SiteAddress,
DispatchInfo: _disp.DispatchDetails,
TorchCB: _disp.TorchCB,
VacuumCB: _disp.VacuumCB,
ReclaimerCB: _disp.ReclaimerCB,
NitrogenCB: _disp.NitrogenCB,
TerminalsCB: _disp.WireNutsCB,
RefrigCapCB: _disp.RefrigCapCB,
CallSTS: _disp.CallSTS,
QuoteSTS: _disp.QuoteSTS,
CustomerSign: CustSign.Image,
CustomerNM: CustSign_CustNM.Text,
CustomerEmail: CustSign_CustEmail.Text,
SendCustEmail: If(CustSign_CustEmail_YesCB.Value, 1, 0),
TechSign: TechSignature.Image,
StartTM: TechSign_StartTM.Text,
EndTM: TechSign_EndTM.Text,
TotalHours: TechSign_TotalHours.Text,
PayRate: TechSign_PayRate.Text,
TechNotes: ForAll(
Filter('[dbo].[DailySWO_DailyTechNotes]',
NoteAssigneeID = _disp.DispatchAssigneeID
) As _tn,
{TechNote: _tn.TechNote,
AreaServed: _tn.AreaServed,
EquipID: _tn.NoteEquipmentID,
EquipMake: _tn.EquipMake,
EquipModel: _tn.EquipModel,
EquipSerialNBR: _tn.SerialNBR,
EquipType: _tn.EquipType,
UnitNBR: _tn.UnitNBR,
UnitSTS: _tn.UnitSTS,
RefrigType: _tn.RefrigType,
RefrigRemoved: _tn.Removed,
RefrigAdded: _tn.Added,
MaterialsUsed: ForAll(
Filter('[dbo].[DailySWO_Materials]',
MaterialAssigneeID = _tn.NoteAssigneeID && MaterialEquipmentID = _tn.NoteEquipmentID
) As _mat,
{MatEquipID: _mat.MaterialEquipmentID,
MatPO: _mat.MaterialPO,
MatQTY: _mat.MaterialQTY,
MatDESC: _mat.MaterialsDESC
}
)
}
)
}
)},
JSON(_data)
)
I hope this is helpful for you.
@Anonymous
The following formula will give you the JSON data you are looking for.
With({_data:
ForAll(
Filter('[dbo].[DailySWO_DailyDispatchWorked]',
DispatchAssigneeID = SelectedAssigneeID
) As _disp,
{AssigneeID: _disp.DispatchAssigneeID,
DisWorkDT: Today(),
TechName: User().FullName,
DisDispatchNBR: _disp.DispatchNumber,
AfterhoursID: _disp.AfterhoursID,
DisDispatchType: _disp.DispatchType,
DisSiteNBR: _disp.SiteNumber,
DisSiteNM: _disp.SiteName,
DisSiteAddress: _disp.SiteAddress,
DispatchInfo: _disp.DispatchDetails,
TorchCB: _disp.TorchCB,
VacuumCB: _disp.VacuumCB,
ReclaimerCB: _disp.ReclaimerCB,
NitrogenCB: _disp.NitrogenCB,
TerminalsCB: _disp.WireNutsCB,
RefrigCapCB: _disp.RefrigCapCB,
CallSTS: _disp.CallSTS,
QuoteSTS: _disp.QuoteSTS,
CustomerSign: CustSign.Image,
CustomerNM: CustSign_CustNM.Text,
CustomerEmail: CustSign_CustEmail.Text,
SendCustEmail: If(CustSign_CustEmail_YesCB.Value, 1, 0),
TechSign: TechSignature.Image,
StartTM: TechSign_StartTM.Text,
EndTM: TechSign_EndTM.Text,
TotalHours: TechSign_TotalHours.Text,
PayRate: TechSign_PayRate.Text,
TechNotes: ForAll(
Filter('[dbo].[DailySWO_DailyTechNotes]',
NoteAssigneeID = _disp.DispatchAssigneeID
) As _tn,
{TechNote: _tn.TechNote,
AreaServed: _tn.AreaServed,
EquipID: _tn.NoteEquipmentID,
EquipMake: _tn.EquipMake,
EquipModel: _tn.EquipModel,
EquipSerialNBR: _tn.SerialNBR,
EquipType: _tn.EquipType,
UnitNBR: _tn.UnitNBR,
UnitSTS: _tn.UnitSTS,
RefrigType: _tn.RefrigType,
RefrigRemoved: _tn.Removed,
RefrigAdded: _tn.Added,
MaterialsUsed: ForAll(
Filter('[dbo].[DailySWO_Materials]',
MaterialAssigneeID = _tn.NoteAssigneeID && MaterialEquipmentID = _tn.NoteEquipmentID
) As _mat,
{MatEquipID: _mat.MaterialEquipmentID,
MatPO: _mat.MaterialPO,
MatQTY: _mat.MaterialQTY,
MatDESC: _mat.MaterialsDESC
}
)
}
)
}
)},
JSON(_data)
)
I hope this is helpful for you.
You are a SAVIOR!!!
One other issue now.. when I try to use that to send to a flow, I get errors. Is this something that you can help me with?
I had to turn the bottom of what you sent to this:
Filter('[dbo].[DailySWO_Materials]',
MaterialAssigneeID = _tn.NoteAssigneeID && MaterialEquipmentID = _tn.NoteEquipmentID
) As _mat,
{MatEquipID: _mat.MaterialEquipmentID,
MatPO: _mat.MaterialPO,
MatQTY: _mat.MaterialQTY,
MatDESC: _mat.MaterialsDESC
}
)
}
)
}
)},
Set(varJSON, JSON(_data))
);
So I could send it to my flow:
'REAL-SWO'.Run(varJSON);
But the flow gives me the following error message:
Unable to process template language expressions in action 'Parse_JSON' inputs at line '1' and column '2397': 'Unexpected token encountered when reading schema. Expected StartObject, Boolean, got StartArray. Path 'schema'.'.
I have it Compose first (so I could get the input), which I copied and used to populate the Parse JSON in the flow.
@Anonymous
You should be able to use the following change to the bottom of the formula:
}
)},
'REAL-SWO'.Run(JSON(_data))
)
Stay away from variables that aren't needed.
Now, as for the error....this is telling you that your flow is expecting a JSON object (record) and it got an array (table), which is correct as far as the formula is concerned as you are sending it a table.
So, the question then is this...are you intending to process a table of records in your flow or just a single record?
And, does the filter of the dispatch table by DispatchAssigneeID = SelectedAssigneeID produce one or more records?
The highest level of data, which is the dispatch/assignee level, will always be 1. The Notes and Materials levels can have multiple each.
This is the output that gets sent to the Flow based on what you gave me (just in case it helps - it's test data only):
[
{
"AfterhoursID": 0,
"AssigneeID": 45404,
"CallSTS": "Complete",
"CustomerEmail": "testcust@testemail.com",
"CustomerNM": "Test Customer",
"DisDispatchNBR": "90702",
"DisDispatchType": "1",
"DisSiteAddress": "3202 N Euclid Ave, Indianapolis, IN 46218",
"DisSiteNBR": "HBH001",
"DisSiteNM": "Him By Her",
"DisWorkDT": "2021-04-12",
"DispatchInfo": "Eniter 3rd floor has no cool ",
"EndTM": "11 am",
"NitrogenCB": 0,
"PayRate": "Regular",
"QuoteSTS": "",
"ReclaimerCB": 0,
"RefrigCapCB": 1,
"SendCustEmail": 1,
"StartTM": "8 am",
"TechName": "Angie Setser",
"TechNotes": [
{
"AreaServed": null,
"EquipID": 43884,
"EquipMake": "Built up",
"EquipModel": "None",
"EquipSerialNBR": "None",
"EquipType": "Air Handler",
"MaterialsUsed": [
{
"MatDESC": "Test Material 1",
"MatEquipID": 43884,
"MatPO": "Test",
"MatQTY": 1
},
{
"MatDESC": "Test Material 2",
"MatEquipID": 43884,
"MatPO": "Test",
"MatQTY": 1
},
{
"MatDESC": "T6 Pro Programmable Thermostat -",
"MatEquipID": 43884,
"MatPO": "L49-157",
"MatQTY": 1
}
],
"RefrigAdded": "",
"RefrigRemoved": "",
"RefrigType": "",
"TechNote": "Test note to build SWO. ",
"UnitNBR": "-fcu01",
"UnitSTS": "Operational"
}
],
"TerminalsCB": 0,
"TorchCB": 1,
"TotalHours": "3",
"VacuumCB": 1
}
]
@Anonymous
Then change the formula to the following:
With({_data:
ForAll(
Filter('[dbo].[DailySWO_DailyDispatchWorked]',
DispatchAssigneeID = SelectedAssigneeID
) As _disp,
{AssigneeID: _disp.DispatchAssigneeID,
DisWorkDT: Today(),
TechName: User().FullName,
DisDispatchNBR: _disp.DispatchNumber,
AfterhoursID: _disp.AfterhoursID,
DisDispatchType: _disp.DispatchType,
DisSiteNBR: _disp.SiteNumber,
DisSiteNM: _disp.SiteName,
DisSiteAddress: _disp.SiteAddress,
DispatchInfo: _disp.DispatchDetails,
TorchCB: _disp.TorchCB,
VacuumCB: _disp.VacuumCB,
ReclaimerCB: _disp.ReclaimerCB,
NitrogenCB: _disp.NitrogenCB,
TerminalsCB: _disp.WireNutsCB,
RefrigCapCB: _disp.RefrigCapCB,
CallSTS: _disp.CallSTS,
QuoteSTS: _disp.QuoteSTS,
CustomerSign: CustSign.Image,
CustomerNM: CustSign_CustNM.Text,
CustomerEmail: CustSign_CustEmail.Text,
SendCustEmail: If(CustSign_CustEmail_YesCB.Value, 1, 0),
TechSign: TechSignature.Image,
StartTM: TechSign_StartTM.Text,
EndTM: TechSign_EndTM.Text,
TotalHours: TechSign_TotalHours.Text,
PayRate: TechSign_PayRate.Text,
TechNotes: ForAll(
Filter('[dbo].[DailySWO_DailyTechNotes]',
NoteAssigneeID = _disp.DispatchAssigneeID
) As _tn,
{TechNote: _tn.TechNote,
AreaServed: _tn.AreaServed,
EquipID: _tn.NoteEquipmentID,
EquipMake: _tn.EquipMake,
EquipModel: _tn.EquipModel,
EquipSerialNBR: _tn.SerialNBR,
EquipType: _tn.EquipType,
UnitNBR: _tn.UnitNBR,
UnitSTS: _tn.UnitSTS,
RefrigType: _tn.RefrigType,
RefrigRemoved: _tn.Removed,
RefrigAdded: _tn.Added,
MaterialsUsed: ForAll(
Filter('[dbo].[DailySWO_Materials]',
MaterialAssigneeID = _tn.NoteAssigneeID && MaterialEquipmentID = _tn.NoteEquipmentID
) As _mat,
{MatEquipID: _mat.MaterialEquipmentID,
MatPO: _mat.MaterialPO,
MatQTY: _mat.MaterialQTY,
MatDESC: _mat.MaterialsDESC
}
)
}
)
}
)},
'REAL-SWO'.Run(JSON(First(_data)))
)
@Anonymous
Yes...see that starts with an array/table of records. The last post I replied should fix that.
Still fails...
Unable to process template language expressions in action 'Parse_JSON' inputs at line '1' and column '2396': 'Unexpected token encountered when reading schema. Expected StartObject, Boolean, got StartArray. Path 'schema'.'.
This is the output that is sent to the Flow with the change:
{"AfterhoursID":0,"AssigneeID":45404,"CallSTS":"Complete","CustomerEmail":"testcust@testemail.com","CustomerNM":"Test Customer","DisDispatchNBR":"90702","DisDispatchType":"1","DisSiteAddress":"3202 N Euclid Ave, Indianapolis, IN 46218","DisSiteNBR":"HBH001","DisSiteNM":"Him By Her","DisWorkDT":"2021-04-12","DispatchInfo":"Eniter 3rd floor has no cool ","EndTM":"11 am","NitrogenCB":0,"PayRate":"Regular","QuoteSTS":"","ReclaimerCB":0,"RefrigCapCB":1,"SendCustEmail":1,"StartTM":"8 am","TechName":"Angie Setser","TechNotes":[{"AreaServed":null,"EquipID":43884,"EquipMake":"Built up","EquipModel":"None","EquipSerialNBR":"None","EquipType":"Air Handler","MaterialsUsed":[{"MatDESC":"Test Material 1","MatEquipID":43884,"MatPO":"Test","MatQTY":1},{"MatDESC":"Test Material 2","MatEquipID":43884,"MatPO":"Test","MatQTY":1},{"MatDESC":"T6 Pro Programmable Thermostat -","MatEquipID":43884,"MatPO":"L49-157","MatQTY":1}],"RefrigAdded":"","RefrigRemoved":"","RefrigType":"","TechNote":"Test note to build SWO. ","UnitNBR":"-fcu01","UnitSTS":"Operational"}],"TerminalsCB":0,"TorchCB":1,"TotalHours":"3","VacuumCB":1}
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!
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
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.
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