Thank you for the feedback. In some of my latest videos, I am trying to improve the audio quality and avoiding any background sound. Check out the latest upload and let me know how you feel about the sound quality: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-ITUFvZkIVQM.html . Do subscribe to the channel to get latest updates.
Good Job, very nice structure. A question is it possible to create a relationship between two fields in two entities. I want to be able to change that the value in either field/entity and the change be reflected in the other field/entity
If it is the same entity, you can use simple Business Rule. In case you are using two different fields in different entities, you can use a flow (Power Automate) which will be asynchronous in nature. In case you want to be synchronous, you may need to create a plugin. A direct relationship between fields in your scenario might not be possible.
Tech Quantum In case we do a plug-in does it need to be a different plug-in every time we have to fields or it can be something that One configured for every time you need to mirror two fields in two different entities
@@jawadsaadi look, it depends on your requirement. Before, you go to create a plugin from developer, make sure all your requirements are ready. In case you introduce a new field, the plugin would need to be modified. If your requirement is just to replicate the fields, I would recommend you to use flows, which even you can configure, if you understand the underlying entity structure.
@@jawadsaadi If you are looking for a freelancer, use the following site to fond professional people, you can get quotes from them and choose the services of whom you like: www.upwork.com/
i have a question here when u create n:n relationship and click on the save and close button then a error occurs and the relationship was not created butt u by pass the error and skip this can u plz elaborate this error thanks regard
Hey, I had the same problem and the issue for me was that the relationship name that I tried to use was not unique beacuse it had the same name as the 1:N relationship. Just change the name of the relationship and it should work
Hi Jam, good observation. I did face that error and as Lukas mentioned below, if you have an existing relationship with same name you will get the error. The relationship name should be unique. I may have taken that step out while editing the video.
