MOSS 2007 Version Test & Hot Fixes

By -
The easiest way to test and verify whether you have the right versions of MOSS in Prod Vs Staging is to do the following :


1. Goto Central Administrator
2. Operations >Servers in Farm> You would find the appropriate version (something like 12.0.0.6421)


Now, check this link on what version/hot fix you need to match the version in Staging or in other environment.


For 2010 Version, follow this link

Comments

Post a Comment

Popular posts from this blog

Power Apps - Restricting the Text Box only Whole Numbers

By Vinod Thachin -
Image
 We can restrict the a Text box to allow only number by making the Format TextFormat.Number as below.  But this will allow decimal Number. We can restrict the Text Box to allow only whole numbers by writing the formulae for the TextBox Onchange as below If(     DataCardValue1.Text <> "" And Value(DataCardValue1.Text) <> RoundDown(         Value(DataCardValue1.Text),         0     ),     Notify("Please enter number without decimals");     Reset(DataCardValue1) )
Read more

Power Apps toPower Automate Error - The input body for trigger 'manual' of type 'Request' did not match its schema definition , the input String does not validate against the date

By Vinod Thachin -
While working with power Apps to Power automate, passing the Date time values as Text(DateTimeValue) throws error as below. The input body for trigger 'manual' of type 'Request' did not match its schema definition. Error details: 'String '' does not validate against format 'date'.'. After checking the Microsoft documentation and few blogs i found out the date values should be passed as a formatted date time. TO pass the date time  we need to use following functions. Text(<<DateTimePicker>>.SelectedDate,"[$-en-US]yyyy-mm-dd") Even after passing the value i am still seeing the same issue and finally found out the default value ids sending as empty and formulae failing for empty values. So we need to make sure the Date Value should not go blank to the formulae and the value should be formatted using the formulae as above. Hope this helps.
Read more

ETAG mismatch (Conflicts exist with changes on the server, please reload)

By Vinod Thachin -
While working with one of the screen Save button, i see error while patching the SharePoint list data. After investigating the issue, I found it is due to old data that is pulled to the screen. As per Mozilla Documentation in the link , ETag is http response header to a version of a resource. It will help to save the time to avoid unnecessary transactions. If there is no changes in the content, it will not send response to the web server. So as there is no change in the List,  Etag will not send response to the web server and it returns the error. So when we save the list it throws error. To avoid the issue, we need to refresh the Data Source in the after Patching the list. In my Case, i have updated the Refresh as below. Path(<< DataSource >>,<< Item to be Updated >>,{<< Column >>:"Yes"}); Refresh( << DataSource >> ); After adding Refresh() function it worked as expected. Hope this helps.
Read more