Navigate function required

[Ahammad_Riyaz]

Hi All,

I have a gallery present it was connected to data source for Dataverse. 

so it will come as a list in gallery.

Here example.

My list is 

Orange

Apple

Mango

So if i click on 

Orange :Navigate Screen1

Apple :Navigate Screen2

Mango :Navigate Screen3

Thanks,

Riyaz

[poweractivate]

@Ahammad_Riyaz 

Yes like this:

Steps:

1.  Screen1 OnVisible

ClearCollect(MyCollection,{Item:"Mango",Screen:Screen4},{Item:"Orange",Screen:Screen3},{Item:"Apple",Screen:Screen2});

This create a mapping of text to the Screen you want it to go to.

2. Make another three screens, all of them with a simple Back Button whose OnSelect goes back to Screen1 - and ideally a matching unique label so you could tell if it is working:

Screen2:

Screen3:

Screen4:

3. Make a button with this Formula for OnSelect:

Navigate(LookUp(MyCollection,Item=Self.Text).Screen);

And "Apple" for the Text property

Notice the button text is used (with Self.Text) to make the Lookup against MyCollection.

The button can be copied again two times, and code can stay the same, just the button text should be changed.

So copy the button two more times, changing one button's text to Orange and another to Mango

There should be a total of three buttons now on the screen, Apple, Orange, and Mango.

4. Toggle between a couple of the screens back and forth to Screen1 so we can try it without saving and publishing and trigger the OnVisible.

You can also move the Screen1 OnVisible to OnStart, and use "Run OnStart" feature if you prefer it.

5. Preview the App and see it working. Or Alt + Click to live preview the app, it works fine

6. To implement another element mapping just add something like 

{Item:"Tango",Screen:ScreenYouWantHere}

to MyCollection

and then just copy the same button and change its Text to Tango.

Make a new screen (if needed) called ScreenYouWantHere

Voila! This new button will then go to the Screen called ScreenYouWantHere!

See if it works for you @Ahammad_Riyaz 

[Ahammad_Riyaz · Accepted solution]

I got the solution if required please refer this.

If(ThisItem.Value = "Screen1",Navigate(Screen1,ScreenTransition.Fade), ThisItem.Value = "Screen2",Navigate(Screen2,ScreenTransition.Fade),ThisItem.Value = "Screen3",Navigate(Screen3,Fade))

[Ahammad_Riyaz]

[poweractivate]

Although it is a good solution, especially if you know it is only going to be done once, if it ever was going to be done more than once for the same string (key) and associated screen (value), it may require hard coding and redefining the same name and the same associated screen yet again and again in many places if you ever need to make this check somewhere else in your app. The information defined would be the same information repeated again and again.

If this pattern ever changed later for a particular key and/or value, it would have to be changed in every single place it was hard coded, whereas the way I did it aims to keep this information in one place (MyCollection) and use it dynamically in one or more places  using Navigate(LookUp(MyCollection,Item=Self.Text).Screen), which during this dynamic usage does not have any specific strings in that formula but instead checks MyCollection.

For example, if you wanted to change which screen some specific string went to, you would need to change every single place where this formula was written manually as it would be redefined manually every time it was used again, whereas in mine you would only need to change the Screen defined for that element in MyCollection and all places where say multiple copies of the button were defined would go to the new screen, since the button code would not have to be changed and is checking the Collection.

However, your solution works as well.

[Ahammad_Riyaz]

Here i was not directly using buttons, i was displaying through gallery and values will be getting from dataverse datasource

[poweractivate]

The principle would be the same, just that instead of Self.Text, it would be something like this  in your case :

Navigate(LookUp(MyCollection,Item=ThisItem.Software_Name).Screen);

Where MyCollection would be:

ClearCollect(MyCollection,{Item:"Client Calling Tracker",Screen:Home_latest_new1});

With some improvement, even the Transition could be defined:

With({lup:LookUp(MyCollection,Item=ThisItem.Software_Name)},Navigate(lup.Screen,lup.ScreenTransition));

Where MyCollection would be:

ClearCollect(MyCollection,{Item:"Client Calling Tracker",Screen:Home_latest_new1, ScreenTransition: ScreenTransition.Fade});

If a Screen or Transition wanted to be overriden for one-off case anyway, the pattern could still be used, but the With can be modified for that element:

With({lup:LookUp(MyCollection,Item=ThisItem.Software_Name)},Navigate(lup.Screen,ScreenTransition.Cover));

//here, this element will always use ScreenTransition.Cover for the Transition instead of the one defined in MyCollection

However, if you are not doing that too often in a pattern, it is probably not worth setting it up the way I did. In that case, I'd recommend your solution instead for the one-off, simple case, or where let's say every string, screen, and transition were so unique and different for every case, that it would be best then to just do what you're doing with just checking it inline.

[Ahammad_Riyaz]

Hi,

i was tried with both are working fine.

Thanks

[Ahammad_Riyaz]

Great Answer.