Will adding a non clustered index to a UDF field in the sales order history table cause any problems within MAS 200 client modules ?

We have a new crystal report that references the largest tables in the database, the sales order header and detail tables, and we had to a UDF field to one of these large tables.

The crystal report references this UDF field to make a calculation, and we experimented with adding a non clustered index in SQL Server on this UDF field in a offline setup that decreased the time to run the crysta report by 50 percent.

Now the million dollar question is, so that we do not affect anything else in MAS 200, is that does simply adding a SQL Server database index to a UDF field cause any problems withing MAS 200 modules anywhere ?

Thanks