Quantcast
Channel: Microsoft Dynamics CRM Forum - Recent Threads
Viewing all articles
Browse latest Browse all 82002

SIlverlight app fails to extract XRM values from Dynamic CRM 2011 Online Fluidic (read optimized) view, whereas it works perfectly in CRM 2011 Online Classic View.

$
0
0

Hi CRM Community,

We are trying to tag a Silverlight Application which uses Xrm Bridge to extract Xrm values from the Dynamics CRM 2011 Online Fluidic (read-optimized) page and displays that in Silverlight control. But to our dismay we found that Xrm bridge is not working in Online CRM 2011 Fluidic view, but the same is working perfectly in Online CRM 2011 Classic view.

This is our sample piece of Silverlight xaml & xaml.cs files.

xaml:-

<Grid x:Name="LayoutRoot" Background="LawnGreen">

<Button x:Name="btnGetXrm" Content="Get XRM Value" HorizontalAlignment="Left" Margin="127,82,0,0" VerticalAlignment="Top" Width="114" Click="btnGetXrm_Click" />

<TextBlock Foreground="Red" x:Name="tbShowXrm" HorizontalAlignment="Left" Margin="83,133,0,0" TextWrapping="Wrap" Text="" VerticalAlignment="Top" Height="28" Width="207" />

</Grid>

 

xaml.cs file :-

namespace XRMTestSilverlightApp

    {

publicpartialclassMainPage : UserControl

        {

public MainPage()

            {

            InitializeComponent();

            }

privatevoid btnGetXrm_Click(object sender, RoutedEventArgs e)

            {     

dynamic xrm = HtmlPage.Window.GetProperty("Xrm");       

dynamic attribute = xrm.Page.data.entity.attributes.get("name");

string Name = attribute.getValue();

tbShowXrm.Text = Name;

            }

        }

    }

This Silverlight app (.xap file) tagged into "Account" record in the CRM 2011 Online Fluidic view, doesnt display xrm values while clicking the button. Whereas the same works in CRM 2011 Online Classic view. Also the background color of lawngreen appears in Classic view but doesn't appear in Fluidic view.

We are stuck on this for a while now and we have release this week. Please share your thoughts on this as soon as possible. What is the reason behind this different behavior across the Classic & Fluidic views and how can we overcome this in Fluidic view?

 

Thanks in advance.


Viewing all articles
Browse latest Browse all 82002

Latest Images

Trending Articles





Latest Images