Contact Us

Comments

Post a Comment

Popular posts from this blog

Display Dataverse Table Data In Power Pages by Using liquid Language

 Display Dataverse Table Data In Power Pages by Using liquid Language Display Dataverse Table Data In Power Pages by Using liquid Language CSS CODE:   /* styles.css */ /* Apply basic styles to the outer container */ .col-md-12.columnBlockLayout {     padding : 16px ;     margin : 60px 0 ;     min-height : 200px ;     background-color : #f5f5f5 ;     border : 1px solid #ddd ;     border-radius : 5px ; } /* Style the table */ .table {     width : 100% ;     border-collapse : collapse ;     background-color : #fff ; } /* Style the table header */ .table th {     background-color : #007bff ;     color : #fff ;     text-align : left ;     padding : 10px ; } /* Style the table rows */ .table td , .table th {     border : 1px solid #ddd ;     padding : 8px ; } /* Apply alternate row background color for better readability */...
Read more

Power Automate OData filter query in SharePoint Get Item

 Power Automate OData filter query in SharePoint Get Item In Power Automate, the OData filter query helps to retrieve only the data that matches specific criteria. Below is an example of how to write it in a flow. Example 1: Filtering SharePoint list items where Status is Approved Let’s assume you have a SharePoint list with a column called Status and you want to filter items where the Status is Approved . Filter Query: Status eq 'Approved' Status : The internal name of the SharePoint column. eq : OData operator for "equals." 'Approved' : The value you are filtering by. Example 2: Filtering records based on dates and another field Suppose you want to filter records where Status is Approved and the Created date is after 2023-01-01 . Filter Query: Status eq 'Approved' and Created gt '2023-01-01T00:00:00Z' and : Logical operator to combine multiple conditions. gt : OData operator for "greater than." '2023-01-01T00:00:00Z' ...
Read more

Understand Solution and Layers

Image
 Understand Solution and Layers In    In Solution, there are two distinct layer levels: Unmanaged layer . All imported unmanaged solutions and unmanaged customizations exist at this layer. The unmanaged layer is a single layer. Managed layers . All imported managed solutions and the system solution exist at this level. When multiple managed solutions are installed, the last one installed is above the managed solution installed previously. This means that the second solution installed can customize the one installed before it. When two managed solutions have conflicting definitions, the runtime behavior is either “Last one wins” or a merge logic is implemented. If you uninstall a managed solution, the managed solution below it takes effect. If you uninstall all managed solutions, the default behavior defined within the system solution is applied. At the base of the managed layers level is the system layer. The system layer contains the tables and components that are requir...
Read more