Une transformation numérique financière est la mise en œuvre et l'utilisation de technologies numériques spécifiquement pour améliorer l'efficience, l'efficacité, la perspicacité, l'agilité et la qualité des processus et systèmes financiers et libérer du temps pour que la fonction financière soutienne l'entreprise avec de meilleures informations et connaissances.

The post Transformation digitale de la fonction finance : où en est-on ? appeared first on iTPro.fr.

Well, I guess these are trends of the modern world and social media, but some of its elements made it to SharePoint lists and libraries. If you work with Date type columns a lot, you probably notice the different styles of date format we have as options. In this article, I would like to explain the two types and how to change them if necessary.

Standard Date Type

The standard date type displays the dates in the form we are used to seeing: Date/Month/Year (or Month/Date/Year depending on the region you leave in).

Friendly Date Type

There is another style available now in SharePoint called Friendly. It displays the dates you often see on social media: yesterday, tomorrow, etc.

How to change data formats in SharePoint lists and libraries

The behavior and default display of date fields depend on the type of Date column you have. There is also a way to change it. The same functionality is available on lists and libraries.

System Columns

For system date columns (i.e., Modified, Created), it defaults to Friendly date type.

To change the format from Friendly to Standard, you must go behind the scenes.

1. From the document library, click Gear Icon > Library Settings
2. Click More library settings
3. Click on the Modified or Created column
4. Change the Radio button to Standard and click OK
5. Your system columns will now display the Standard date and time in the document library

Custom Columns

When you create custom date type columns, they default to Standard format. However, you can change the type to Friendly right when you create a column.

1. Click Add column > Date and time
2. Give your Date column a name. You will notice it defaults to Standard.
3. This is what it looks like with the Standard date type
4. To change the format from one type to another, you can just use the modern interface to do so
5. And this is what a custom column looks like with the Friendly date type

The post Friendly vs. Standard Date format in SharePoint lists and libraries appeared first on SharePoint Maven.

Depuis quelques temps, on remarque de plus en plus de sujets dans la presse spécialisée, et des conversations dans les cercles d’initiés gravitent autour de la notion de jumeaux numériques.

The post Jumeaux numériques : Buzzword ou tendance à prendre au sérieux ? appeared first on iTPro.fr.

Parmi les défis des Chief Data Officers, on observe un recentrage sur les fondamentaux et mais aussi des tendances qui vont éclairer les orientations des CDO.

The post Les 8 tendances de la Data et de l’IA en 2023 appeared first on iTPro.fr.

Euclyde Datacenters, entreprise française exploitant six datacenters interconnectés et de haute disponibilité sur le territoire national, confirme son positionnement sur le marché des datacenters souverains de nouvelle génération. Eclairage avec Anwar Saliba, Directeur général d’Euclyde Datacenters.

The post Euclyde Datacenters, un fort positionnement sur le marché des datacenters souverains appeared first on iTPro.fr.

SharePoint Online provides a powerful search engine that enables users to quickly find the information they need. However, the quality of search results depends largely on how well the site is optimized for search. In this blog post, we’ll explore some best practices for optimizing your SharePoint Online site for better search results and also discuss PowerShell scripts that can help you achieve this.

Use Managed Metadata:

Managed metadata is a hierarchical collection of centrally managed terms that can be used to tag content in SharePoint Online. By using managed metadata, you can ensure that your content is consistently labeled, which can improve the accuracy of search results. PowerShell script can be used to create and manage term sets and terms.

Customize Search Refiners:

Search refiners are used to filter search results based on specific criteria such as file type, author, or date. By customizing search refiners, you can make it easier for users to find the information they need. PowerShell script can be used to create custom refiners based on managed metadata.

Optimize Page Titles and Descriptions:

The page titles and descriptions are used by the search engine to index the content of the page. By optimizing these elements with relevant keywords, you can improve the visibility of your pages in search results. PowerShell script can be used to update page titles and descriptions.

Use Friendly URLs:

Friendly URLs are human-readable web addresses that are easy to remember and type. By using friendly URLs, you can make it easier for users to find your content and improve the visibility of your site in search results. PowerShell script can be used to set friendly URLs for pages and sites.

Enable Searchable PDFs:

PDF files are a common format for documents, but they are not always searchable by default. By enabling the searchability of PDF files, you can ensure that their content is included in search results. PowerShell script can be used to enable PDF search in SharePoint Online.

By following these best practices and using PowerShell scripts, you can optimize your SharePoint Online site for better search results. PowerShell scripts can help you automate the process of managing and optimizing your site for search, making it easier and more efficient to achieve your search optimization goals.

The post How to optimize SharePoint online Search for better for better results appeared first on MS Technology Talk.

One of the capabilities we recently got in Project for the Web is the ability to have custom fields within a project schedule. So today I want to explain how to create custom fields in Project for the Web.

What is Project for the Web?

Project for the Web is a Microsoft application available within Microsoft 365 that allows organizations to manage projects. It fills the gap between Planner, which is more of an informal task management application, and Microsoft Project, which is a desktop project management application that is sophisticated in terms of capabilities but also a bit confusing and not unintuitive to regular users. I actually compared the various task management options within Microsoft 365 in this article, so check it out.

Example of a schedule in Project for the Web

Built-in fields in Project for the Web

Project for the Web already contains some built-in fields (columns) that you can add/display on any project. Essentially, these are core columns/fields that are either necessary for the Project for the Web to work/function or allow for some additional capabilities in terms of project tracking.

Some built-in fields include Start, Finish, Duration, % completed, Assigned to, and a few others.

When you create a new project, some fields are displayed by default in a Grid, and you can always show/hide others by clicking on the + Add column.

How to create custom fields in Projects for the Web

Just like we can create custom metadata in SharePoint lists and libraries, we can also create custom columns in Project for the Web Task schedules. In Project for the Web, we call these custom metadata fields. Here is how to create a new custom field.

1. Click the Add column button, then + New Field
2. On the next screen, choose the type of column you want to create and its name
3. As of the writing of this post, only certain types of columns are supported (shown below)
4. For this article, I would like to add a Cost column (number field), to track the cost of each task on my schedule. The roll-up question is whether or not the numbers for the subtasks will be added together (rolled up/summed up) on the parent tasks.
5. In my case, I will choose to sum up all the subtask costs (roll-up). You may select other math functions as well (i.e., show the min or max, or an average of the task numbers).
6. Click Create to create the field
7. The custom field will now appear in the schedule
8. By the way, in case you chose roll-up, this is what it looks like. In my case, I chose Roll up Sum of all subtasks, so it totals up the numbers (costs in my case) for the parent task.

How to fill in information for the custom fields in Project for the Web

If you want to fill out the custom fields with specific task information, you do so by filling it out like any other field on a task. You have two options:

• Option 1: Complete the information by filling out a field in the Grid mode (like you do in Excel)
• Option 2: Click in the Task Details Panel and complete the information there

The post How to create custom fields in Project for the Web appeared first on SharePoint Maven.

Habitudes des collaborateurs, gestion des données numériques, considérations écoresponsables… Les Français sont conscients de l’impact écologique des activités numériques professionnelles, mais la moitié persiste dans ses habitudes peu vertueuses…

The post Ecoresponsabilité numérique : entre conscience et habitudes … appeared first on iTPro.fr.

Microsoft 365 security is a big topic. Focus is important when it comes to getting things done. In this article, we suggest five areas that administrators could work on during 2023 to improve the security posture of their tenant. You might already have established full control over some of these areas. Even if you have, it's still good to consider if you can improve security.

The post Five Things Microsoft 365 Security Administrators Should Do in 2023 appeared first on Practical 365.

When you create a Managed Metadata column, you have to point the column to a term set within a Term Store. As I documented in one of my previous posts, you can either create term sets globally, within the tenant-wide term store or locally at the site level. Each option has its pros and cons, so today, I want to compare the two.

Tenant-Level Term Sets

Tenant-Level Term Sets are created within the Term Store that is accessible via the SharePoint Admin Center. It can also be accessed by the site owners as we; however, for site owners to be able to adjust the values within the terms sets or create new terms sets, they need to be granted Manager or Contributor roles within the Term Store. Below I would like to list the advantages and disadvantages of this option.

Advantages

• By design can be accessed and seen by all the SharePoint sites within a tenant

Disadvantages

• For the site owners to create new terms sets, they need to be set up as group managers or contributors (by the SharePoint Administrator or other Group Managers of the term group)
• Requires SharePoint Admin Role to be set up/configured

Site-Levet Term Sets

As described in a previous post of mine, site owners can also create site-level terms sets as well. This though, becomes the only option if they can’t get access to the SharePoint Admin Center (which is a headache in larger organizations).

Advantages

• The only option for site owners to use when they can’t access their company’s SharePoint Admin Center
• Pretty straightforward to use

Disadvantages

• By design, term sets created at the site level are not visible to other sites within a tenant. For other sites to see the term sets, they need to be shared with other sites (manually). I described the mechanism here.

The post Site-Level vs. Tenant-level Term Sets appeared first on SharePoint Maven.

Depuis l’apparition de la crise liée au COVID-19, le monde du travail n’a cessé d’évoluer et ces dernières années ont vu émerger deux tendances en la matière qui ont touché le monde entier et qui s’ancreront certainement dans la durée.

The post L’exploitation des données RH, réponse à la pénurie de talents ? appeared first on iTPro.fr.

Today I want to describe a feature in modern SharePoint that allows you to connect two lists and libraries and dynamically filter them based on the value selected from one of the lists or libraries. I know this all sounds a bit confusing, so let Dr. Zelfond explain this.

Use Case

Perhaps it first makes sense to explain what I am talking about. Say you have two lists. One is a list of clients with the corresponding client information (client name, address, status, etc.).

Another list is a list of contacts for each client (client name, first and last name of contact, email address, and phone number).

I want to be able to view both lists at once on a SharePoint page, but the way I want this to work, I want to select a client name from the Clients list, and I want the second list to automatically filter the contacts based on client name selected from the first one. Thanks to the dynamic filtering option we now got in SharePoint Online, we can do this. Let me explain.

How to connect and dynamically filter lists and libraries in SharePoint Online

1. Edit the Page and add both lists to the page, side-by-side
2. Once added, it should look like this
3. Edit the page again, and select the list you want to be filtered based on the choice made in another list (in my case, Contacts). Click the pencil icon.
4. Next, enable the Dynamic filtering toggle. You will see several drop-downs appearing underneath. In the first drop-down, choose the column in the list you want automatically filtered. In my case, I want my Contacts list to be filtered by Company Name. Next, choose the list or library where you will filter the information. In my case, it is a Clients list. Finally, select a column that you will filter in that second list. In my case, it is Client Name. So essentially, the column in the first drop-down and the column in the third drop-down have to match in terms of the information they contain (Company Name = Client Name). Click Apply.
5. Republish the page

How dynamic filtering works

Now that we connected two lists via dynamic filtering let’s see how it works. Click on any row from List 1, and you will notice that List 2 is filtered based on the selection made.

Use Cases for using dynamic filtering

Dynamically connect a list to a list

You can quickly build a quick CRM within SharePoint, by connecting a list of clients with a list of contacts (just as I described above) and even deals/opportunities all presented on the same page.

Dynamically connect a list to a library

You can maintain a list of clients and then have a document library with, say, contracts, all tagged against a given client name, and then have those contracts filtered automatically based on a client selected from the list.

Notes

• You can dynamically connect two lists or two libraries or a list and a library
• The column headings do not need to match. For example, I can have a Client Name heading in list/library 1 and a Customer Name in list/library 2. The main thing is that the choices/information in those columns must match!
• Related to the above, the text/choices need to match 100% for this work. For example, if in list 1 you spelled out ABC Inc. and in list 2 you called the same company ABC, Inc. (with a coma), those do not match, and dynamic filtering won’t pick it up.

The post How to connect lists and libraries via dynamic filtering in SharePoint Online appeared first on SharePoint Maven.

Microsoft 365 tenants can create Azure AD accounts in different ways. No matter whether you create accounts manually or with PowerShell scripts, the important thing is to end up with the right data in Azure AD because many Microsoft 365 features depend on accurate directory.

The post The Importance of Standardizing Microsoft 365 Account Creation appeared first on Practical 365.

I thought this might be useful to share , we run into an issue where we used the new command bar editor to create new buttons and All was good till we added a new column to the same table and published all customisations, went to the Command Bar and tried to set the visible property using Power FX formula but unfortunately the new column did not show up.

So by contacting Microsoft this is a known issue as of now and as a work around you need to follow the below steps:

1. Go to the Solution -> Choose the app ->Select the table -> Right Click Edit Command Bar.

3. Choose the Command Bar you want to Edit

4. Select your customised button and click Open Component Library

5. Component Library will be loaded on the Menu Click File -> Save , Then Publish and then reopen the Command Bar ,your metadata will be refreshed.

[xml]$termXML = Get-Content "C:\Legal.xml"
($termXML.SelectNodes("//*")) | Where {$_.Owner -ne $null} | `
ForEach-Object {$_.SetAttribute("Owner", "i:0#.f|membership|admin@MOD******.onmicrosoft.com")}

Connect-SPOSite -Url "https://mod******.sharepoint.com"
Import-SPOTaxonomy -InputFile $termXML -ParentTermStore (Get-SPOTermStore)

Azure Hybrid

In earlier MVPLABSerie blogpost I wrote about making your on-premises Servers hybrid with Azure Arc enabled Servers.
In my mvplab.local domain, there is a SQL 2022 Cluster running which also has the Azure Connected Machine Agent version 1.24.

One of the benefits of Azure Arc enabled Servers for SQL is that you can do on-demand SQL Health assessments on your SQL Environment in your On-premises Datacenter. In the following step-by-step guide we will prepare the SQL Cluster nodes.

Go to this link to watch the video

In my mvplab.local domain I’m doing the following steps :

Go in the Azure Portal to Azure Arc
Click on SQL Servers under Infrastructure.
Click on Add

I Choose for Connect Servers
because both SQL Nodes are already connected in my MVPLAB.local domain.

Prerequisites
Click on Next Server details.

Select the right Azure Subscription and Resource Group
Select the region and Operating System
Set Proxy server URL if you need one
Click on Next.

Set your owner tags if needed.
Here you can find more information about Tags Management

From here you have to download the Script
and Run it locally on both SQL Nodes. ( or your Single SQL Server )

Run the script in administrator modus of Powershell ISE.
go to page https://microsoft.com/devicelogin
and enter the Code

Login and continue.

Here you see that the Azure Connected Machine Agent already is installed.
But it will now add the SQL Extension.

Installation Completed Successfully.

Now we have two Azure Arc enabled SQL Servers connected.

Overview of SQL 2022 Node in Azure Arc.

You can see the Databases running.

Here you can set your Admin from Azure Active Directory.

But we want to do a SQL Assessment, but the Azure Monitoring Agent is still missing.

Here you see that the SQL extension is installed.
Now we will add the Azure Monitor Agent to my existing Log Analytics Workspace.
Click on Add

Select Log Analytics Agent – Azure Arc.

Add your Workspace ID
Add your Workspace Kay
Click on Review + Create

Validation Passed.

Azure Monitoring Agent is Installed.

From here you can do the On-Demand SQL Assessments via
Microsoft Azure Arc enabled SQL Servers.

The SQL Server Assessment focuses on several key pillars, including:

• SQL Server configuration
• Database design
• Security
• Performance
• Always On
• Cluster
• Upgrade readiness
• Error log analysis
• Operational Excellence

Example of SQL Server Assessment results.

On each assessment result you get a recommendation from Microsoft so you can make your SQL environment Health and Secure!

Conclusion

To get these health results of your SQL environment is Awesome You are in control of your Azure Hybrid Arc enabled SQL Servers to keep them Healthy and Secure. The following Azure Arc enabled SQL Server blogpost is about Azure Defender for Cloud for your SQL Servers. With these two Azure Arc for SQL Server features you get the best Insights to keep your data as save as possible.