The following is the comparison of data type supported by the rollup, calculated and Power Fx in Power Apps
| Rollup | Calculated | Power Fx |
| – | Single line of text | Single line of text |
| – | Choice | – |
| – | Yes/no | Yes/no |
| Whole number | Whole Number | – |
| Decimal number | Decimal Number | Decimal number |
| Currency | Currency | – |
| Date and time | Date and time | Date and time |
Source:
The following is an excerpt on restoring Power Platform environments
To restore to a production environment, you must first change its type to sandbox.
You can set a sandbox, production, or trial (subscription-based) environment in administration mode so that only users with System Administrator or System Customizer security roles are able to sign in to that environment.
Administration mode is useful when you want to make operational changes and not have regular users affect your work, and not have your work affect end users (non-admins).
You can optionally disable background operations such as all asynchronous operations including Dataverse workflows and email server-side synchronization.
The following is an excerpt regarding the backups of Power Platform.
System backups occur continuously and aren’t counted towards capacity.
If you use Microsoft Power Platform to create production environments that have a database and Dynamics 365 applications enabled, you can benefit from the system backups that are automatically performed for those environments. The system backups are stored for up to 28 days.
For environments that don’t have Dynamics 365 applications enabled, the default backup retention period is only seven days. However, for managed environments, admins can use PowerShell to change the setting and extend the backup retention period. The available options are 7, 14, 21, and 28 days.
All environments, except Trial environments are backed up.
Automated system backups are great, but you should make your own backups before making significant customizations or applying a version update.
About manual backups:
When a user tries to create new embed codes using the “Publish to Web” feature, he/she/them will get the error “Contact your admin to enable embed code creation”.
The reason behind this issue is, Microsoft changed the default state of “Publish to web” setting in tenant admin settings. Previously it used to be “Allow existing and new codes” and now it’s “Only allow existing codes”
The fix is simple, just change the settings to “Allow existing and new codes” and users should be able to publish to web.
But wait still the security issue exists. Any user can publish to the web and the report data is exposed to any user on the Internet who has access to the report URL. So the best course of action is to enable the additional security settings, which is “Apply to” “Specific security groups”. Once enabled, only users from a specific security group will be able to create embed codes using “Publish to web”.
For more documentation on the settings, please visit Microsoft Docs