Hello Employer,
Recruit from over 1 Crore candidates in 2 Simple Steps
1. Post Requirement and Get Calls from Matching Candidates at NO COST
2. Discuss Face-to-Face and Recruit in 3 Days!!
Join the Community of 5 Lakhs Employers/HRs who have trusted WorkIndia.
What are you waiting for? Click Here https://workindia.in/dl/recruit-staff
Regards,
Jatin Jakharia
Co-Founder, WorkIndia
This is a simple blank master page
<%-- Identifies this page as a .master page written in Microsoft Visual C# and registers tag prefixes, namespaces, assemblies, and controls. --%>
<%@ Master language="C#" %><!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<%@ Import Namespace="Microsoft.SharePoint" %>
<%@ Register Tagprefix="SPSWC" Namespace="Microsoft.SharePoint.Portal.WebControls" Assembly="Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="PublishingWebControls" Namespace="Microsoft.SharePoint.Publishing.WebControls" Assembly="Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="PublishingNavigation" Namespace="Microsoft.SharePoint.Publishing.Navigation" Assembly="Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register TagPrefix="wssuc" TagName="Welcome" src="~/_controltemplates/Welcome.ascx" %>
<%@ Register TagPrefix="wssuc" TagName="DesignModeConsole" src="~/_controltemplates/DesignModeConsole.ascx" %>
<%@ Register TagPrefix="PublishingVariations" TagName="VariationsLabelMenu" src="~/_controltemplates/VariationsLabelMenu.ascx" %>
<%@ Register Tagprefix="PublishingConsole" TagName="Console" src="~/_controltemplates/PublishingConsole.ascx" %>
<%@ Register TagPrefix="PublishingSiteAction" TagName="SiteActionMenu" src="~/_controltemplates/PublishingActionMenu.ascx" %>
<%-- Uses the Microsoft Office namespace and schema. --%>
<html>
<WebPartPages:SPWebPartManager runat="server"/> <SharePoint:RobotsMetaTag runat="server"/>
<%-- The head section includes a content placeholder for the page title and links to CSS and ECMAScript (JScript, JavaScript) files that run on the server. --%>
<head runat="server">
<asp:ContentPlaceHolder runat="server" id="head">
<title>
<asp:ContentPlaceHolder id="PlaceHolderPageTitle" runat="server" />
</title> </asp:ContentPlaceHolder> <Sharepoint:CssLink runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderAdditionalPageHead" runat="server" />
</head>
<%-- When loading the body of the .master page, SharePoint Server 2007 also loads the SpBodyOnLoadWrapper class. This class handles .js calls for the master page. --%>
<body onload="javascript:_spBodyOnLoadWrapper();">
<%-- The SPWebPartManager manages all of the Web part controls, functionality, and events that occur on a Web page. --%>
<form runat="server" onsubmit="return _spFormOnSubmitWrapper();">
<wssuc:Welcome id="explitLogout" runat="server"/>
<PublishingSiteAction:SiteActionMenu runat="server"/>
<%-- The PlaceHolderMain content placeholder defines where to place the page content for all the content from the page layout. The page layout can overwrite any content placeholder from the master page. Example: The PlaceHolderLeftNavBar can overwrite the left navigation bar. --%> <asp:ContentPlaceHolder id="PlaceHolderMain" runat="server" />
<asp:Panel visible="false" runat="server">
<%-- These ContentPlaceHolders ensure all default SharePoint Server pages render with this master page. If the system master page is set to any default master page, the only content placeholders required are those that are overridden by your page layouts. --%>
<asp:ContentPlaceHolder id="PlaceHolderSearchArea" runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderTitleBreadcrumb" runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderPageTitleInTitleArea" runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderLeftNavBar" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderPageImage" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderBodyLeftBorder" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderNavSpacer" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderTitleLeftBorder" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderTitleAreaSeparator" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderMiniConsole" runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderCalendarNavigator" runat ="server" />
<asp:ContentPlaceHolder id="PlaceHolderLeftActions" runat ="server"/>
<asp:ContentPlaceHolder id="PlaceHolderPageDescription" runat ="server"/>
<asp:ContentPlaceHolder id="PlaceHolderBodyAreaClass" runat ="server"/>
<asp:ContentPlaceHolder id="PlaceHolderTitleAreaClass" runat ="server"/>
<asp:ContentPlaceHolder id="PlaceHolderBodyRightMargin" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderTitleRightMargin" runat="server" />
</asp:Panel>
</form>
</body>
</html>
Thanks,
Rajesh Batchu,
Share Point Developer,
Desk # :+1 409 945 1295
GV # :+1 23456 4 234 8
Mobile# :+1 40 9692 9692
Arya Vysyas (Telugu: ఆర్య వైశ్యులు, Kannada: ಆರ್ಯ ವೈಶ್ಯರು, Oriya:କୁମୁଟୀ) or Komatis are a Telugu speaking Vysya (trading) caste fromAndhra Pradesh. They are also found in Karnataka, Tamil Nadu, Maharashtra and Orissa. The people of this caste are mainly into business and trading activities. Arya Vysyas are strict vegetarians.[1] Orthodox Vysyas follow rituals prescribed in the Vasavi Puranamulu, a text written in the late medieval times (4). Sri Vasavi Kanyaka Parameswari Devi is the main Goddess or Kula Devatha of Arya Vysyas. Here is a small List of Telugu Vysyas.
Arya Vysyas use the suffix Setty in Andhra Pradesh and Karnataka, and Chetty in Tamil Nadu. Some members of the community are also known to use the suffix Guptha or Gupta. Arya Vysyas in Maharashtra are found in greater numbers in Marathwada and Vidarbha regions. They almost exclusively speak Marathi as their mother tongue and have adopted largely Maharashtrian customs. Their last names typically are like Polawar, Palkrutwar, Raiwar, Mungilwar, Gujalwar, Kankanwar, Yadawar, Pattewar, Revanwar, Raiwar, Yerremwar, Wattamwar, Bidwai, Chalikwar, Papinwar, Chidrewar Gundawar, Pampatwar, Pokalwar, Rathkanthiwar etc. Some uncommon names are also found in Maharashtra like Lade, Kole, Kotgire, Mahajan, Gadam, Kottur, Chidri etc. Varaganti's and Varanasi's are some other famous surnames in Telangana Region. But ancestors of such families are known to be speaking Telugu; There are lot of Telugu families residing in Telangana areas of Andhra Pradesh bordering with Maharashtra for many generations, who have such surnames, They are Telugu Arya Vysya's residing in Telangana region of Andhra Pradesh adjacent to Maharashtra state. In Orissa also many Komatis are staying for generations.Their surname are Patra,Subuddhi,Senapati,Rao etc.They speak a mixture of Oriya with Telugu. In karnataka they speak kannada & somewhat telugu, their surnames are Jajee, Gada, Chidri, Mailapur, Ainapur, Amman, Bacha, Pola, Kotarki.
Origin of Vysyas
A large number of Vysyas are said to have originally lived and still live in large numbers on the banks of the Godavari River (7). One of the local names for the river is Gomati or Gomti. It is believed that people who lived on the banks of the Godavari River were called Gomati, which later become corrupted as Komati.
Arya Vysya etymologyArya Vysyas, also known as Gavara Komatis (9), are one of the 3 subsets of the Komati grouping. The other 2 are Kalinga Vysya and Thrivarnika. While Arya Vysyas are vegetarian, the Kalinga Vysyas and Thrivarnikas are non-vegetarians (8). Arya Vysyas are distributed throughout Andhra Pradesh, Karnataka, Tamil Nadu and Maharashtra. Kalinga Vysyas are mostly spread around Srikakulam and Vizianagaram districts of Andhra Pradesh and Orissa, whereas Thrivarnikas are small in number and spread in small pockets of Vizianagaram,Visakhapatnam, East Godavari and Warangal districts.
According to Thurston (1975) Komati is derived from "go-mati" or possessor of cows and their main occupation was protecting cows (6) . The book Religion in Andhra: a survey of religious developments in Andhra from early times up to A.D. 1325, page 175 mentions that the merchant classes preferered Jainism for gaining social status and respectability, and the erstwhile vanijas (merchants) became Komatis or followers of the Gomatha cult in the medieval times.
Another book Social mobility in Medieval Andhra by BSL Hanumantha Rao, page 176 mentions an alternative etymology for the word Komati as a "derivation of the word from Gomatha (Gomateshwara), the great Jaina Saint, and it implies that they were followers of Gomatha cult or were originally Jains". The book Socio-cultural history of ancient and medieval Andhra, page 130, mentions that "The story of Vasavi, the caste goddess of the Vaisyas narrated in the Vaisya Purana appears to have definite Jain overtones".
The book Socio-cultural history of an Indian caste, by C. Dwarakanath Gupta, page 10, mentions that "the tradesmen from Gouda desa took to Jainism and adopted the Gomata cult. The word Gomata got distorted to Gomatlu, Komtulu. In Malayalam and Tamil, the word Komati is in use. The Jain Vysyas gave up Jainism and embraced Vedic religion during its revival".
Inclusion into the vaishya varnaThe book Religion and public culture: encounters and identities in modern South India by John Jeya Paul and Keith E. Yandell (page 33 to 55) details the inclusion of Komatis into theVaishya varna during the colonial times. It noted that Komatis desired to be members of the Vaishya varna in the colonial times. However Niyogi brahmin councillors who controlled the powerful Mandri Mahanad did not accept the claim.
Attempts by Komatis to adopt orthodox Vaishya rituals drew the hostile attention of Niyogis. When a Komati family in Masulipatnam (Machilipatnam) announced its intention to performUpanayanam (sacred thread) ceremony for their son, leaders of the Mahanad invaded the house, polluted the fire and stopped the ceremony. Violence encounters along these lines leading to loss of lives were noted in 1784, 1803, 1809, 1817 and 1820.
Of the approximately 1000 Komati families living in Masulipatnam in 1825, the Gavara Komatis (who later registered their caste name as Arya Vysyas in 1905) were one of the two main Komati groups. They had 102 gotras, which were not considered to correspond in identity with the gotras deemed appropriate for Brahmanas or Vaishyas. From 1784 to 1825 few families organized the upanayanam, but by 1825 majority of the caste's males wore the sacred thread.
The upanayanam ceremonies were officiated by the Vaidiki Brahmins who were tolerant of the wishes of their patrons. However, the Niyogis continued to mobilize the untouchables (Dalits) to riot, and organized their offensives against such ceremonies. This led three Komati litigants to take their complaints to the civil court. One litigant, Mamidi Venkataryulu had studied the Dharmashastras and took a leading role in Komati activities with regard to the upanayanams. They were supported by the Vaidiki brahmins.
The Niyogis and their lawyers attempted to destroy the Vaidiki support in court by arguing that the Vaidikis were unread in the dharma shastras; and that they supported the Komatis because they depended on Komati fees for their livelihood. In 1833 the Sadr Adalat decided in favour of the Niyogis. In 1845 the Judicial Committee of the Privy Council refused to make a formal decision.
The Magistrates of Masulipatnam continually received charges from Komatis and Niyogis and could not manage the dispute. The Magistrates attempted to solve the dispute by asking Komatis to stop performing the rituals. The Komatis however remained unfazed by the court orders and kept going with their attempts.
By the beginning of the 20th century, it was common for the Komatis to describe their clan membership in terms of brahmanical rishi gotras. And in the 1901 census the komatis - significant numbers of whom had prospered in the 19th century - were the only Telugu community who succeeded in getting the government to rank them as Vaishyas (5). Following this inclusion, a group of Komatis established the South India Vaisya Association in 1905.
HistoryBetween 1921 to 1931, the Viceroy of Madras Presidency had implemented a commission which helped the people in their community to register their community with changes in the name if any. The South India Vaisya Association (1905) registered their community as Arya Vysyas..(provide further details).
Sri Vasavi Kanyaka Parameshwari Devi Puranamu as written in TeluguSouth India is the Treasure House of many temples. Among them Sri Vasavi Kanyaka Parameswari temple situated in Penugonda, a town in the West Godavari District of Andhra Pradesh. The temple is a fascinating multi-colored (Gali Gopuram) seven storied tower with a beautiful architecture. This Penugonda Kshetram is considered as the 'Kasi of Vysyas' and is a holy place for Vysyas.
Kusuma Sresti or Setty was the Setty king of Vysyas also known as Pedda Setty (Elder among Settys) whose territory was a Vassal state of Vengi desha, which was ruled by Vishnu Vardhana (Vimaladitya Maharajulu). His capital was Penugonda (Jestasailam) city for all the 18 paraganas during 10th and 11th century A.D. He and his wife Kusumamba were considered an ideal couple and led a peaceful domestic life. They worshiped Lord Siva (Nagareswara Swamy) as the part of their daily duties.
Though they had been married for many years, the couple did not have peace of mind as there was no successor to the kingdom. Their many prayers and sacrifices did not bear fruit and hence they were grief stricken. They approached their Kula guru (family Teacher) Bhaskar Acharya also a Komti who was well versed in shastras and by virtue of his profession was treated as a Komti Bramhana. He advised them to perform Puthra Kamesti Yaga, which Dasharatha had observed.
During the auspicious hour, the couple started the yaga. The Gods were pleased and sent prasadam (blessed fruit from god) through Yagneswara (fire God). They were told that they would beget children after eating prasadam. With devotion they ate the Prasadam and within a few days the signs of pregnancy was found with Kusumamba. She expressed unusual desires, which indicated that she would give birth to children who would fight for the welfare of all.
Birth of Vasavi DeviDuring spring season, there was pleasure everywhere. Amidst this beauty, Kusumamba gave birth to twins, one male the other female on Friday the tenth of Vaisaka (Telugu month) at twilight during convergence of Uttara Nakshatra and Kanya (Virgo). The male child was named Virupaksha, and the female Vasavamba. During childhood, Virupaksha showed the features of becoming a powerful king, whereas in Vasavi, the inclination towards art & architecture, adoration music and philosophical approach were seen.
Under the guidance of Bhaskaracharya, Virupaksha learnt the Puranas, fencing, horse riding, martial arts, archery, statecraft etc.., which were essential to rule his Territory. Vasavi learntfine arts and mastered philosophy and was proud to be an intelligent woman.
Vishnu Vardhana RajuWhen Virupaksha attained proper age he married Rathnavathi, daughter of Aridhi setty of Aelur Town. The huge gathering thought that even Vasavi's marriage would one day also be observed with the same pomp and grandeur.
When King Vishnu Vardhana went on expedition to expand his empire, he visited Penugonda, where King Kusumasresty received him and took him in a procession and arranged a felicitation program in the colorful auditorium. After Manamathan (God of Romance) threw his sweet arrows on him, Vimaladitya (Vishnu Vardhana) spotted Vasavi among the crowd and fell madly in love with her. He felt he could not live without her and was determined to marry her. He sent a minister to enquire about her. The desire of Vishnuvardhana (Vimaladitya) was like a death blow to Kusumasresty. He was neither in a position to accept it nor to deny. The fact that the Emperor was already married, was much older, the difference in caste and the fact that he was not in a position to prevent this from occurring all caused extreme stress for Kusumasresty.
He discussed these issues with his closest family and friends and they unanimously decided to let Vasavi decide. Vasavi frankly expressed her desire to be a Virgin throughout her life and intended not to concentrate on worldy matters.
Kusumasetti sent a denial message to king Vishnuvardhana. The king was furious and sent a Battalion with orders to attack mercilessly and to get Vasavi for him. The brave Komti's of Penugonda by using the techniques of Sama, Dhana, Bheda and finally Danda, defeated Vishnuvardana's army.
Community reactionAt this crucial juncture, Kusumasresti called for Great Conference of the Chief of all the 18 cities and the leaders of all 714 Gotras in the presence of Komti Kula Guru Bhaskaracharya.
In the conference, there was difference of opinion. The Chiefs of 102 Gotras made a firm decision thought that "Those who are born must die and cowards die many times before their death but the valiant taste death but once. Even if the opponent is stronger, can't the spark burn a heap of straw? Hence, let us fight for a good cause. Whereas, the leaders of the other 612 gotras felt that the matrimonial alliance would be safer and more beneficial."
Bhaskar Acharya said: "We must safeguard our respect even at the cost of our lives". These words acted as a catalyst for Kusumasresti. Even though they formed a minority he was determined not to give his daughter Vasavi in marriage to the king. With this incident, the unity of the Komti's was broken. The Emperor, like an injured Cobra, took the lead of his huge army with strong determination to destroy his opponents. In Penugonda necessary arrangements were made with the supporters of the 102 Gotras to face the consequence.
Vasavi Devi's reactionVasavi, entered into scene and said: "Why should there be bloodshed among ourselves for the sake of a Girl? Why sacrifice the lives of soldiers for our selfish desire. It is better to give up the idea of war. Instead, let us rebel in a novel way. We can control war through non-violence and self-sacrifice. Only people with strong will power and moral strength can participate in this kind of self- sacrifice. Vasavi's new idea was delightful to her parents and they decided to act in accordance with Vasavi's directions.
Athmam BalidhanaAs per the directions of Vasavi, at the holy place of Brahmakunda on the banks of Godavari, the royal servants arranged 103 Agnikundas (fire pits) in a special way. The whole city was observing that day as a festival day. Then Vasavi asked the couples of the 102 Gotras: "Will you plunge into this holy fire along with me?" Everyone of them whole heartedly gave their consent. They suspected Vasavi must be an incarnation of God and requested her to show her real nature or swarupa.
She smiled and revealed her true self, which had the glittering radiance surpassing the brightness of sun. She said: "I am the incarnation of Adiparashakthi." To safeguard the dignity of woman and to protect Dharma, to destroy Vishnu Vardhana and to reveal to the world the magnanimity of Komti's I come here in Kaliyuga. Like Sati Deva who was insulted entered into holy fire, I too plunge into the holy fire and enter the other world. Kusumasresty during last birth was a great Saint by name Samadhi as per his aspirations he could attain salvation along with the people of 102 Gotras. That is why I asked you all to undergo Athmam Balidhana." Vasavi advised the gathering about patriotism, honesty, social service, and tolerance etc.
Vishnu Vardhana's deathDevi disappeared as soon as the divine words came out of her mouth and people saw her in human form. Then all of them entered into holy fire after meditating upon their Gods.
Though Vishnuvardhana felt bad Omens, he marched ahead and reached the main entrance of Penugonda. Then his detectives reported what all had happened in the city. He could not bear the great shock and his heart shattered into pieces. He fell down vomiting blood and he was no more.
The self-sacrifice of Vasavi and the end of Vishnuvardhana was the talk of the town. People condemned the deeds of Vishnuvardhana and appreciated the epoch maker Vasavi and her non-violent principle (1).
Sri Vasavi Devi's legacyThe son of Vishnuvardhana, Raja Raja Narendra rushed to Penugonda and repented about the incident. Later on Virupaksha consoled him and said: "Brother, let us learn and formulate the present and future on the strong base of past. Vasavi had come to rescue of the people without giving room for great bloodshed. Her non-violence gave a good result", hence forth Komatis shall not fight or rule states but shall engage in the service and as well wishers of others including services like trade, agriculture etc..,
Virupaksha visited many pilgrim centers like Kasi, Gaya and other under the guidance of komti kula guru Baskaracharya. To commemorate the pilgrimage they installed 101 lingas for each gotra in Penugonda. Then, Narendra installed a statue of Vasavi as a token of respect. From that day onwards all Komti's began performing poojas to her and is considered as Komatikula Devatha-Vasavi Kannika Parameswari.
Vasavi's life is worth remembering because of her faith in non-violence religious values and her defense of status of women. She became immortal as she has been mainly responsible for the propagation of reputation of Komatis throughout the world. Vasavi is an epitome for aryan women who sacrificed her life than to inter marry with the black skinned Dravidian kings of that time when vysyas moved south and hence the community of komatis who followed her have now rechristened themselves and their community as Arya Vysya's.Vasavi, who had rejected worldly pleasures, won the minds of Komatis and is the champion of peace and non-violence and is remembered by the faithful.[2]
GothrasThere are 714 gotras before agnipravesham of vasavi matha now there are 102 gotras among Arya Vysyas. They followed 102 Rishis for conducting their rituals. Surname gotras and Rishis for identification and classification for all the Arya Vysyas are one and the same. The gotras is equivalent of the Sanskrit names of Rishis.[3]
Groups of Arya Vysyas became followers of particular Rishi for conducting their rituals and they claimed to be the followers of that particular Rishi. Thus they are identified by the Rishi name. And for still feature identification they use a pre-fix surname generally indicating the area from which they migrated or the profession to which they belong and other such identification.
1. AGASTHYASA anubha Gula, anubala, anubala Gula
2. ATHREYASA ARASAKULA- ARISISHTAKULA-ELISISHTAKULA- ARISETLAKULA-HARISISHTAKULA
3. ACHAYANASA AKRAMULAKULA- AKYAMULAKULA- AMALAKULA- ARKYAMULA
4. UGRASENASA KUMIRISISHTA- KUMARSISHTA- KOMARSISHTAKULA
5. UDHGRUSHTASA KANYAKULA- KANUKULA- KRANUKULA- KRANU
6. UTHAMOJASA UTHAKALAKULA-UTHAKULA- UTHASISHTAKULA- UHTAMAKULA
7. RUSHYASHRUNGASA ANANTHAKULA
8. AUSHITHYASA YANASAKULA- YAANASAKAKULA- YAANASABIKULA
9. GANVSA GARNAKULA
10. GANDHARPASA SARAKULA- SEKOTLAKULA- SEGOLLA- SAMANAKULA- SHRESHTA KUNDALA KULA
11. KABILASA MANDU- MANDHAKULA- HASTHAKULA- MANDAKULA
12. KABEEDHASA VENKALAKULA
13. KASYABASA GANAMUKU KULA
14. GUTHSASA ISHVAKU KULA
15. KOUNDINYASA KANALOLA- KANASRILA- KANASRILA KULA
16. GOUNDHEYASA KAMASISHTA
17. KOUSIKASA KARAKA PALA
18. KRUSHNASA DHANAKULA- THANANAKULA- THENUKULA
19. GARKYASA PRAHEENUKULA- PRAHEENIKULA- PAIPIKULA
20. GRUTHSAN MATHASA ESABAKULA- ESUBAKULA- ESHUBAKULA- SANNAKULA- JANAKULA- JYANUKULA
21. GOPAKASA INJTHAPAKULA- GOPAKULA- KONDAKULA- KONDAKAKULA
22. GOUTHAMASA GANTHISEELA- GANTHASEELAKULA- GANTHASEELA- GRANTHISEELA
23. CHAKRAPANISA CHAKRAMULAKULA- CHAKRAMULASAKULA
24. CHAMARSHANASA BETHASHRESHTA- BETHAKISHTA- PATHASISHTAKULA- PATHTHASISHTAKULA
25. JADABARATHASA KUNDAKULA- DHURASISHTA- DHURASISHTAKULA
26. JADHUKARNASA CHANDRAKULA- CHANDRAMOOLA- CHANDRAMASISHTA
27. JAMBASOOTHANASA THRIMULA- THRIMULAKULA
28. JARATHKARASA SANTHAKULA- JANAKULA- JYANUKULA
29. JABAALISA SIRISISHTAKULA- SIRASISHTAKULA
30. PAPREYASA SANASISHTA- SANASISHTAKULA- SINISHETLA
31. JEEVANDHISA BURHTILASISHAKULA- BRUMASISHTAKULA- LRUTHTHIKULA
32. THARANISA THRIVIKRAMA- SISHTASA- THRIVIKRAMASISHTAKULA
33. THITHIRISA PAMTHAKULA- PRAHTAMAKULA- PRAVATHAKULA
34. THRIJADASA UPARAKULA- USIRAKULA
35. THAITHREYASA SITHURUBELLU- SITHRUBELLU- SITHRUBA- SITHRUBAKULA
36. THALPYASA PADINAKULA- PLAKAKULA- PALAKALAKULA- PADANASISHTAKULA
37. DHURVASASA THITHISA- THITHINAKULA- THENTHSULA- THENTHASALA- THETHANAKULA
38. DHEVARATHASA HAARAASIKULA
39. DHEVA KALKYASA USIRAKULA- DHESISHTAKULA
40. NARADHASA PALAKAKULA- PALAKULA
41. NETHRA PAHTASA SANDHOKU- SANDHOKULAKULA
42. PARAS PARAAYANYASA DHUVVISISHTAKULA- POULATHATHSYA KULA- SRIBHUMSIKULA
43. PALLAVASA KANAPAKULA- KANTAKULA- KANTAASUKULA- KANTASUUKULA- KANTASTHULAKULA
44. PAVITHRA PAANISA DHAYASISHTAKULA- DHAYAA SISHTAKULA- DHASISHTAKULA- THAISETTAKULA- THESETLAKULA- THESISHTAKULA- THYSISHTAKULA
45. PAARAASARYASA KAMATHENUKULA- PATAKASEELAKULA- PANCHALAKULA- PANCHALLAKULA- PRANASEELAKULA- PRANUSEELAKULA- PRANA SEELA KULA- PAMPAALLA
46. PINGALASA AYANAKULA
47. PUNDAREEGASA ANUSISHTA- ANUSISHTAKULA- KRANUKULA- THONDIKULA
48. BHOODHI MASHASA DHURVADIKULA- DHULAASISHTAKULA- DHURYADAKULA- DHULASISHTAKULA- DULASIKULA- DHODAKULA- DHODILULA
49. POUNDRAKASA BUMSIMAMSUKULA- BUMSIMANAKULA- BROSISHTAKULA- BROSI- BROLEKAKULA
50. POULASTHYASA GOSEELA- UTHAMAGOSEELA- PALLALAGOOSEELA- PADUGOSEELA- SRIGOSEELA-PUNAGOSEELA- SOORYAKULA- UTHAMASEELA- PUNAGORSEELA- PATTUGOSEELA- PUNAKASEELAKULA BHEEMAGOSEELA- SATHYAGOSEELA- CHANDHIGOSEELA-
51. PRASEENASA VANISISHTAKULA- LENASISHTAKULA- LELISISHTAKULA
52. PRABHADHASA UDHVAHAKULA- PENDLIKULA- RAVISISHTAKULA
53. BRUHATHATHVASA PERUSISHTA- BERISISHTAKULA- BHYRUSISHTAKULA
54. BHODHAYANASA BHUDHIKULA- BHDHANAKULA
55. BHARADHVAJASA BALASISHTA- BALASESHTA- BALISISHTA
56. BHARGGAVASA PRUTHIVISISHTA- PRUTHIVISRESHTA
57. MANTHAPALASA VINNASA- VINNAKULA- VINUKULA- VENNAKULA
58. MAANAVASA MATHYAKULA- MANYUKULA-MARAASAKULA- MAANAACHAKULA
59. MAREECHASA THISHAMASISHTAKULA- THEESHMAKULA- THEESHMASISHTAKULA- THEESHMASHRESHTA
60. MAARKANDEYASA MONUKULA- MORUKA- MORUSA- MORKKALAKULA,MOORKULA
61. MUNIRAJASA PADMASISHTASA- PADMASISHTAKULA- PADMASHRESHTA
62. MAITHREYASA MATHTHIKULA- MATHANAKULA- MATHYASAKULA- MITHUNAKULA- MAITHRIKULAv
63. THOUMYASA CHANDA- CHANDHAKULA- CHANDAKAKULA- CHANKALAKULA
64. MOUNJAYA MUNJEEKULA- MOUNJRISA- MOUNJIKULA
65. MOUTHKALYASA NAABILLA- NAABEELAKULA- NAABEELASAKULA- MUNIKULA- MOOLAKULA
66. YAASKASA VYALAKOOLASA- VELGOLLA- VAELIGOLLA
67. YAGNA VALKYASA ABIMANCHIKULA
68. VADUGASA ANUMARSHANAKULA
69. VARADHANTHUSA MASANTHA- MASANTHA - MASANTHAKULA - MASHANTHAKULA
70. VARUNASA YELASISHTAKULA- VELASISHTAKULA- VELISISHTAKULA- SIRISISHTAKULA
71. VASHISHTASA VASTHI- VASTHISA- VASTHIKULA- VASTHRIKULA
72. VAMADEVASA UPALAKULA- UPAMAKULA- UPANAKULA- UPAMANYAKULA
73. VASUDEVASA BHEEMASISHTA- BHEEMASISHTAKULA- BHEEMASRESHTAKULA
74. VAYAVYAYA MRANGAMAKULA- VRAHASISHTAKULA- VRAKALAMULA- VRANGAMAKULA- VRANGAMULAKULA
75. VALMIKASA SUKALAKULA- SAKALLAKULA- SUCHALAKULA- SUGOLLAKULA
76. VISHVAGSHENASA UBARISISHTA- VIBARISISHTA
77. VISVAMITHRASA VIKRAMASISHTA- VIKRAMASISHTAKULA
78. VISHNUVRUNTHASA PIPPALAKULA- PUPPALAKULA
79. VAIROHITHYASA VASNTHA- VASANTHAKULA
80. VYASASA THANAKU- THANATHAKULA
81. SARABANKASA KRAMASISHTA- KRAMASISHTAKULA- KRAMASHRESHTAKULA
82. SAARGNARAVASA KUNDAKAKULA- KONDAKAKULA
83. SHANDILYASA THUPPALA- THUPPALAKULA
84. SRIVATHSASA SILAKULA- SRIRANGAKULA- SRILAKULA
85. SRIDHARASA SIRISHESHTA- SIRISHESHTAKULA-SRISHISHTA
86. SHUKLASA SRISALAKULA- SRISALLA- SRISALLAKULA
87. CHOWCHEYASA ILAMANCHIKULA- YALAMANCHIKULA- HELAMANCHIKULA
88. CHOWNAKASA KAMALAKULA- DHRUGASISHTA- DHRUGASISHTAKULA- THANATHAKULA- CHAANAKALAKULA- CHOWNAKA
89. SATHYASA ANTHIRAKULA- CHINTHAKULA- CHINTHAMASISHTA CHINTHYAKULA- CHINTHALA
90. SANAKASA SHANAKULA- SANAKULA
91. SANATHKUMARASA DANKARAKULA- MUTHUKULA
92. SANANTHANASA SAMASISHTAKULA
93. SAMVARTHAKASA RENDUKULA- RENTAKULA
94. SUKANCHANASA PUCHAKULA- PUCHAKASEELA- PUNITHA- PUNEETHASA- PUNTHAKULA
95. SUDHEESHANASA DHANTHAKULA- DHYANTHAKULA- DHVANTHAKULA- DHENTHAKULA- DHEVISETLA- DHONTHAKULA
96. SUNDHARASA INA- INAKULA- INAKOLA- VINUKULA
97. SUVARNASA PRODAYASAKULA- PRODAJAKULA- PROUDAAYAJA
98. SUBHRAMHANYASA SANTHANAKULA- SANIKTHAKULA
99. SOWBARNASA PUTHURUKULA- PUTHURUKSAKULA
100. SOWMYASA HASTHIKULA
101. SOWVARNASA CHUSALAKULA- SAKALLAKULA- SOOCHALAKULA- SOOKASALLAKULA- SOOSALAKULA
102. HARIVALGAYASA KAPATA- KURATA- KORATAKULA- GORANTAKULU
Use run command - >
%windir%\assembly\gac_msil
and Place the respective dll and pdb file in the given assembly folder. and start debugging the event handler.
Getting to know the Data Form Web Part
Series Information
Getting to know the Data Form Web Part (1 of 4)
What is the Data Form Web Part?
This article is the first in a four part series on the Data Form Web Part. First things first - what is the
Data Form Web Part (DFWP)? The easiest place to start is that the DFWP is a Web Part that can be
added to any SharePoint site. Unlike most Web Parts, however, the DFWP cannot be (easily) added
through the web browser - it must be created using SharePoint Designer.
Components of a Data Form Web Part
Before we jump into creating a DFWP, it is helpful to understand the components that make up a DFWP.
There are three main components of any Data Form Web Part:
Data Source The DFWP supports many different data sources including:
• SharePoint Lists and Libraries
• An XML File
• ODBC/SQL Database
• Web Service
Or a combination of sources using a Linked Source
Parameters Parameters can be used to make your DFWP more dynamic. The DFWP can read
parameters from several sources including the Query String, Form fields, and cookies.
XSL Simply put, this is what defines how your DFWP displays. The DFWP uses an XSLT
stylesheet to transform data into HTML (for more information on XSL see the XSL page
at the W3C: http://www.w3.org/Style/XSL/)
Table 1 - Components of a Data Form Web Part
Creating a Data Form Web Part
To create a Data Form Web Part, you will need to open a page on a SharePoint site using SharePoint
Designer:
Figure 1 - An .aspx page in SharePoint Designer
To insert a Data Form Web Part, first select a Web Part Zone and choose Insert Data View from the Data
View menu:
Figure 2 – Data View Menu
A Data Source Library Task Pane will appear displaying the available data sources for the current site:
Figure 3 - Data Source Library
In this example we’ll select an existing SharePoint List called “Stuff” and choose the Show Data option:
Figure 4 - Previewing the data in a Data Source
The Data Source Details will appear in the Task Pane displaying the fields from our list:
Figure 5 - Data Source Details for a SharePoint List
We can now select the fields we would like to display in our Data Form Web Part. By clicking on fields
while holding Control, we can select multiple fields and then choose to insert those fields as a multiple
item view:
Figure 6 - Inserting fields into a Data Form Web Part
We now have a Data Form Web Part:
Figure 7 - Data Form Web Part in SharePoint Designer
Next you will want to save your page. When you save, you will receive a prompt:
Figure 8 - Site Definition Page Warning
This prompt does not indicate an error; it simply warns you that saving will customize the page. If you
are not familiar with customizing pages (formerly referred to as “unghosting”) in SharePoint I highly
recommend clicking the “About SharePoint site definitions” link.
Once saved, your Data Form Web Part will look very similar to an out of the box List View Web Part:
Figure 9 - Data Form Web part in Internet Explorer
Behind the scenes
If we modify our new Data Form Web Part in Internet Explorer, we can see some of what is happening
behind the scenes. Click on the Web Part Menu and select Modify Shared Web Part:
Figure 10 - Modifying our DFWP in Internet Explorer
In the Web Part Task Pane you will see two properties you can edit:
Figure 11 - DFWP properties
These two properties (XSL Editor and Parameters Editor) map to the components we discussed earlier in
Table 1. Note that you cannot change the Data Source outside of SharePoint Designer. If you click on
the XSL Editor, you will see the XSL that was generated for you by SharePoint Designer:
Figure 12 - Viewing the XSL of a DFWP in Internet Explorer
While the XML can be pretty tough to look at, the good news is that even if you are not an expert at XSL,
if you have some HTML background you will be somewhat familiar with what you are seeing. For
example, in the section I’ve captured in figure 13 you can see that we have a few table cells. Inside of
those cells we are using some XSL markup to output the Title and Color fields. For the Quantity field, we
are first running a format-number function, and then displaying the output.
Figure 13 - XSL from a Data Form Web Part
While it is possible to make changes to the DFWP from Internet Explorer, in practice you will make most
of your changes in SharePoint Designer.
Configuring the Data Form Web Part
If we want to configure our Data Form Web Part in SharePoint Designer, the easiest way is to open the
Common Data View Tasks menu by clicking on the chevron in the top-right corner of our DFWP:
Figure 14 - Common Data View Tasks
From the Common Data View Tasks menu we can add, remove, or reorder columns in our DFWP. We
can also apply filters and add sorting along with many other options. For now, let’s explore how you
could use Parameters in a Data Form Web Part. If you click on the Parameters… link, you will open the
Data View Parameters dialog:
Figure 15 – Data View Parameters dialog
In this example we’ll add a Color parameter that reads from the Query String:
Figure 16 - New Color Parameter
Now that we have created the parameter, we can now configure a filter for our DFWP. Back on the
Common Data View Tasks menu; select Filter to open the Filter Criteria dialog:
Figure 17 - Filter Criteria dialog
Now we’ll configure our DFWP to filter using our new parameter:
Figure 18 - Filter by color
Once our filter is applied SharePoint designer applies the filter to our live preview. Because we did not
set a default value for our Color parameter, we are presented with the “No Matching Items” template:
Figure 19 - DFWP “No Matching Items” template
To allow you to once again view what your DFWP would look like, select the “Show with sample data”
option in the Common Data View Tasks Menu:
Figure 20 - DFWP option: Show with sample data
Now if we view our page in the browser and pass in a parameter we can see that our filter has been
applied:
Figure 21 - DFWP with filter applied in the browser
Conclusion
As you can see, the Data Form Web Part is a highly configurable Web Part that allows you to quickly
create highly customized views of your data. In my next article we will explore some of the more
advanced views you can create using the Data Form Web Part.
Getting to know the Data Form Web Part (2 of 4)
Advanced Data Form Web Parts
In the first article of this series we introduced the components of a Data Form Web Part. One of the
core components of a Data Form Web Part is the XSL which defines how the DFWP will render. You can
customize the XSL to change how the DFWP is displayed but before we jump into customizing the XSL
code let’s take a look at what SharePoint Designer can do for us.
Conditional Formatting
Data Form Web Parts support conditional formatting which allows you to apply formatting and visibility
rules to html elements. To work with conditional formatting you’ll need to open the Conditional
Formatting task pane on a page with a Data Form Web Part. To open the task pane, open the Common
Data View Tasks menu by clicking on the chevron in the top-right corner of our DFWP and then select
Conditional Formatting:
Figure 1 – Opening the Conditional Formatting task pane
You should then see the Conditional Formatting task pane and usually one existing condition:
Figure 2 – The Conditional Formatting task pane
Note that the create button is disabled because we have not selected an HTML element to apply any
conditional formatting to. Let’s create a new Conditional Formatting rule that will change a table row’s
background color based on the color selected in the list. First, we need to select a row (which isn’t
always as easy as it sounds). If you are lucky, you can position the mouse just right to give you the
option to select a row. I find it is easier to simply select a cell and then choose select row from the
menu:
Figure 3 – Selecting a Table Row
Once you have selected a row you should also see a selected <tr> in the Quick Tag Selector:
Figure 4 – The Quick Tag Selector
At this point you are ready to add a conditional formatting rule. Choose create from the Conditional
Formatting task pane and choose Apply formatting...
Figure 5 – Opening the Conditional Formatting task pane
Next we need to define when the formatting will occur by defining the condition. In this case we’ll apply
formatting when the Color field is set to Red:
Figure 6 – Adding Condition Criteria
Now we are presented with the Modify Style dialog. From here we can define what to do when our
condition is met. In this case, we’ll just set the background color to red:
Figure 7 – Applying a style to your Conditional Formatting
Once we press OK, our conditional formatting is revealed using SharePoint Designer’s live preview:
Figure 8 – Live preview of Conditional Formatting in action
Behind the scenes
So what is really going on here? It isn’t Magic - it is XSL. Select your row again (if it isn’t already
selected) and switch to the code view. The corresponding html for the row you selected should be
selected in the code view as well:
Figure 9 – XSL <tr> definition
The part we’re really interested in is highlighted below:
Figure 10 – Conditional Formatting applying style to a <tr>
For those of you that don’t read XSL, the attribute tag is used to add an attribute to the parent tag. In
this case it is adding a style attribute to our TR tag. The value of the style attribute is determined by the
XSL "if" statement which determines if the @Color element is equal to the text value Red.
Digging into XSL
Now that we can see what’s going on, let’s change the XSL to make it a little more useful. We have
several colors defined in our list so we probably don’t want to define a separate condition for each
color. Another option is to use the XSL "choose" tag:
Figure 11 – Updating the XSL by hand
The XSL "choose" tag allows us to configure multiple conditions and results. The downside is that we
lose the ability to see direct XSL customizations reflected in the Conditional Formatting task pane. It
does, however, allow much more complex rendering:
Figure 12 – Conditional Formatting in action
Not just pretty tables, my friend
A lot of people that are new to the Data Form Web Part use conditional formatting and custom XSL to
create dashboards with highlighted lines (etc), however, that’s not all the Data Form Web Part is good
for. Some other examples I have seen include:
• Generating customized Mobile views of SharePoint lists
• Displaying Flash (.swf) files stored in a document library
• Generating JavaScript that interacts with page objects such as Google/Live Maps, Windows
Media Player, etc
Conclusion
The ability to customize the XSL of a Data Form Web Part is what makes it such a powerful tool for
displaying data in SharePoint. In my next article we will focus on the FORM in Data Form Web Part as
we look at how to edit and save data using the Data Form Web Part.
Getting to know the Data Form Web Part (3 of 4)
Editing and Saving Data using the Data Form Web Part
In the previous article of this series we looked at how we can change the way a Data Form Web Part
displays using Conditional Formatting. One thing we haven’t looked at yet is the reason we call it the
Data Form Web Part - its ability to edit and save data.
Editing List Data
First we’ll look at adding the editing abilities to a Data Form Web Part. We’ll start by opening a Web
Part page SharePoint Designer. With the Web Part Page open, select “Manage Data Sources” from the
Data View menu:
Figure 1 – Manage Data Sources
Next, select the data source you’d like to use and choose “Show Data” from the context menu:
Figure 2 – Show Data
Select the fields you want to use for your Data Form and select “Multiple Item Form” from the “Insert
Selected Fields as” dropdown:
Figure 3 – Insert Multiple Item View
Now that we have a read-only view, click the chevron on the Data Form Web Part and select “Data View
Properties” from the Common Data View Tasks menu:
Figure 4 – Common Data View Tasks
On the Editing tab, select the options to support editing and inserting of items:
Figure 5 – Data View Properties Editing Tab
Now when you browse to the page you will have the ability to edit items inline:
Figure 6 – Using a Data Form Web Part
You also have the ability to add new items without leaving the current Web Part page:
Figure 7 – Inserting from a Data Form Web Part
You also have the ability to build a page that allows editing multiple items at once. Before we get to
that, let’s review how to add a new Web Part page to our site using SharePoint Designer.
Adding Web Part Pages to your Site
To add a new page we’ll start by right-clicking the root of our site in the Folder List and selecting New,
and then ASPX to create a new .aspx page:
Figure 8 – New ASPX Page
Next we’ll attach a master page to our new ASPX page:
Figure 9 – Attach a Master Page
Select OK to attach the site’s default Master Page to the new page:
Figure 10 – Select a Master Page
Now we can open the "branded" page and modify the PlaceHolderMain region to allow us to insert a
Web Part Zone:
Figure 11 – Override PlaceHolderMain
Now choose to insert a Web Part Zone into the PlaceHolderMain content region:
Figure 12 – Insert Web Part Zone
With our new Web Part Zone inserted we’re now ready to create add a Data Form Web Part.
Building a Custom Data Form
To add a Data Form Web Part, select Manage Data Sources from the Data View menu and bring up the
Data Source Library Task Pane:
Figure 13 – Manage Data Sources
Next we’ll select a list and select Show Data:
Figure 14 – Data Source Library Task Pane
Now we can select the fields we would like to have on our form (using control/shift to select multiple
fields). Once we have our fields selected, hit the Insert Selected Fields as dropdown:
Figure 15 – Insert DFWP
In this example we’ll select Multiple Item Form. Now we have a custom edit form for our list:
Figure 16 – Data Form Web Part
One of the powerful features of the Data Form Web Part is the control you have over how the fields
render. By selecting a DateTime field and selecting the chevron, for instance, you can modify the
DateTime formatting options to control how the date is formatted:
Figure 17 – DateTime Formatting Options
These kinds of formatting options, along with the greater control over the form’s layout make the Data
Form Web Part an extremely powerful tool.
Conclusion
As you can see, the Data Form Web Part is much more powerful than its predecessor, the Data View
Web Part. Using SharePoint Designer and the Data Form Web Part you can quickly build no-code
applications that read and write data from multiple data sources. In my next article we will take a look
at how you can trigger workflows from a Data Form Web Part.
Getting to know the Data Form Web Part (4 of 4)
Data Form Web Parts and Form Actions
In this series we’ve looked at how to create powerful displays using the Data Form Web Part and how to
interact with that data. For this article we’ll explore how to take that interaction to the next level by
triggering Workflows from a Data Form Web Part.
Introducing Form Action controls
For a quick demo of Form Action controls I’ve created a Data Form Web Part from a simple XML file:
Figure 1
This list is nice but it would be even better if we could somehow trigger a workflow to send an email to
people on the list to say “Happy Birthday.” To get started we’ll open the page in SharePoint Designer
and edit our Data View. The first change we want to make is to add a new column to our Data View:
Figure 2
Next we want to add our Form Action control. Choose “SharePoint Controls” from the Insert menu and
then select “More SharePoint Controls.”
Figure 3
This should open the Toolbox task pane and display the various SharePoint Controls that are available.
The control we are interested at the moment is the Form Action Button (although later make sure you
try out the Form Action Hyperlink):
Figure 4
Select the Form Action Button and drag it into the new column we have created. Once the control has
been added to the page a Form Actions dialog will open:
Figure 5
From this dialog you can add a number of actions. For this example we’ll skip to the most powerful
option. Select [Custom action] and choose Add. Next, click settings and a familiar dialog will launch:
Figure 6
If you have worked with SharePoint Designer workflows before you will be very familiar with this screen.
The interesting thing to note here is that we have just created a SharePoint Designer workflow that is
NOT associated to a SharePoint list or library.
Now that we’ve given that some thought, let’s get back to the task at hand and actually make our
workflow do something! From the actions dropdown select “Send an email.” Next click “this message”
to configure your email:
Figure 7
For now we’ll hard-code the form fields and press OK to save the changes. Next click Finish to save your
workflow changes and OK to save your Form Action changes. Now preview the changes in the browser
and test your form by clicking on the Form Action button:
Figure 8
If you do not receive the email and believe your workflow was configured properly you may want to
check the workflow history list for any errors. The workflow history list is a hidden list by default so you
have to manually type in the path: http://site/web/Lists/Workflow%20History
In my case, outgoing e-mail settings for the server have not been configured so I receive an error
message in the workflow history list which is pretty helpful:
Figure 9
Well, even if email was configured properly we wouldn’t want to hard-code the email address field since
we have a perfectly good value saved in the XML file. Back in SharePoint Designer let’s update our Data
View to allow us to pass the current record’s email value into our workflow. To do this, we’ll need to
change the format-as option of the email field by clicking the field’s chevron:
Figure 10
Switching the field to display as a Label turns what was rendered as just text into an ASP.NET Label
control. Now that our Data View has an ASP.NET form control available, let’s edit our Workflow. There
are two ways to update our Workflow:
1) Right-click on the Form Action button and select Form Actions to re-open the Form Actions dialog:
Figure 11
2) Expand the Workflows folder and open the .xoml file of the matching Workflow (Custom Form Action
1, in this case):
Figure 12
When you are working with form fields I’ve found that it is usually best to use method #1 mentioned
above. Once you are back in the Workflow Designer, click on your email action to configure your
settings. Clear out the To: field and click on the address book icon to launch the Select Users dialog.
From the Select Users Dialog, choose Workflow lookup:
Figure 13
From the Define Workflow Lookup dialog, select Form Fields as your source and you should see a form
field that matches our email column:
Figure 14
Save your changes and return to the Workflow Designer screen. Before we leave here, let’s make sure
we can see who we’re sending our message to by adding an additional action to log the same field to
the history list:
Figure 15
Save your changes and test out your form again. If you go out to your Workflow History list you should
see an entry that logs the email address your message would have been sent to as well as any errors
that may have occurred:
Figure 16
Working with List Items in Form Action Workflows
Our first example showed how easy it is to create workflows that aren’t associated with any SharePoint
lists. That is a pretty powerful option but really since we’re in SharePoint it would be nice to know how
to do something similar with list data. For our last example we’ll look at how to add a form action
button that marks an item in a task as complete AND puts its % complete field at 100%.
For this example I’ve created a simple tasks list and a Data View showing my tasks:
Figure 17
Our first step is to make sure we can uniquely identify our task in a workflow. Ideally we would key off
of the list item’s ID but unfortunately that is more difficult than it should be in the current version of
SharePoint Designer. In this scenario we can assume that our Title fields are unique so we will start by
converting that field into an ASP.NET Label:
Figure 18
Next we’ll create a new column and add a Form Action Hyperlink control to the column. By default the
form action has a “Navigate to page” action defined. First modify that action and configure the target
page to be the current form page:
Figure 19
We do this to get around a little timing issue that happens when we update items using Form Action
Workflows. Speaking of updates, next add a [Custom action] and move it to the top of the Current
Actions list. Then click Settings to configure the Workflow. From the Actions dropdown, select Update
List Item and click on the action to configure it. On the Update List Item screen configure the list we
want to configure and add the fields and the values we want to set. Finally, configure the “Find the List
Item” section to match the Title field to the title control on the corresponding row we clicked on.
Figure 20
When you choose OK you will be warned that the criteria we set to find the appropriate list item to
update may not be unique. Again, for this scenario we’re assuming titles will be unique so we can select
Yes. Save and preview your changes and you should see your Form Action Hyperlink:
Figure 21
After clicking on the Form Action Hyperlink for Article 4 you can see that my % Complete is updated as
well as my status:
Figure 22
Next you could certainly update the Data View so it conditionally displays the Form Action Hyperlink
only on rows where the tasks are not marked complete. You could also extend the Form Action
Workflow so an email notification is sent with a customized message to both the creator of the task and
the “Assigned To” user.
Conclusion
Form Actions and Form Action Workflows are powerful extensions of the Data Form Web Part. Using
the lessons learned in this series you can now create powerful displays of data, work with external data
sources, and create dynamic workflows.
Displaying SharePoint Fields by Permission Level
There are situations where certain fields in lists or libraries need to be hidden or displayed according to the permission level of the logged in user. Since there is really no out-of-box way to assign permissions to fields, here's a way to do it using conditional formatting in SharePoint Designer. This is my favorite SP Designer trick, that I discovered a few months ago.
See my reference (Ian's SharePoint Blog):
In this example, the field called "Priority" needs to be hidden from everyone except for those users who have rights as approvers on this custom list. Also, there is a field called "Audit Date", that only approvers need to be able to edit, but other users (even those with edit rights) should not be able to edit this field, and everyone can see it.
Doing this entails creating custom forms for all three forms (NewForm, DispForm, and EditForm) in the list.
Here goes...
1. To keep this simple, create a custom list called "Policies" on your site. There are 4 fields:
Policy Name (changed from the default Title field)
Priority - multiple choice
Notes - multiple lines of text
Audit Date - date/time
http://spinsiders.com/laurar/files/2009/01/capture1.jpg
2. Create a blank web part page in the same site collection as the Policies list. It doesn't matter where you save it, since we'll be deleting it later.
3. Open this web part page in SharePoint Designer. Click on "Click here to insert a Web Part". This is really just to make sure that you insert this web part into a web part zone, and not some random spot on the page.
4. On the <Insert> menu, choose SharePoint Controls, then Custom List Form.
5. Pick the Policies list, then choose New Item Form. OK
6. Select the entire table row that contains the Priority field. This is the field that we want to hide from everyone except approvers. On the <Data View> menu, choose Conditional Formatting.
http://spinsiders.com/laurar/files/2009/01/capture2.jpg
7. In the Conditional Formatting screen on the right, click <Create>, and choose <Show content>. On the Condition Criteria screen, click <Advanced...>
http://spinsiders.com/laurar/files/2009/01/capture2.jpg
8. Select IfHasRights from the list of functions, and then put the number 16 in the parentheses. To see where I got the number 16 (approver permissions), click on the link to Ian's blog above. Click OK. Click OK again.
http://spinsiders.com/laurar/files/2009/01/capture3.jpg
http://spinsiders.com/laurar/files/2009/01/capture3.jpg
9. Next, the Audit field needs to be only editable by list approvers. So, since this is the new item form, we'll just hide it from everyone else. So, select the Audit Date row, and put the exact same condition on it with conditional formatting.
10. Save this page. It's okay to customize it from the site definition.
11. At this point, it does help to have some data in your form, so go ahead and create a couple of list items.
Also, I'd like to note that when using custom forms like this, the Attachment button doesn't work anymore. I think there are blogs somewhere about this bug, but I've never tried fixing it.
12. Create a new, blank web part page in the same place you created the first one. This will be the EditForm page. Repeat steps 3 & 4. Then, this time when inserting the Custom List form, select "Edit item form".
13. Repeat steps 6, 7, and 8 on the priority row.
14. Next, we essentially need to make two copies of the Audit Date field. We want it to be editable to list approvers, and visible (not-editable) to anyone else. Create a new row in the table.
15. Put the text "Audit Date" in the left cell, and put the cursor in the right cell. In the <Data Source Details> pane on the right, select the Audit Date field, then click Insert selected field as --> Formatted --> DateTime. Then, you can opt to uncheck the Time check box, and click OK.
16. Select the row of the editable audit date field. For the conditional formatting, only show the content when IfHasRights(16).
17. Select the row of the read-only date field (the one that was inserted in step 15), and create a conditional formatting rule to HIDE content when IfHasRights(16).
At this point, since you most likely have full control permissions on this list, this row will seem to disappear! While you're doing this design work and showing/hiding fields, you can go to the Conditional Formatting pane, and click Set Visibility and choose All Formatting hidden. This will let you see the field you just hid. Be sure to set it back to default when you're done.
HANG in there, only one more form to go.
You know the drill... create another blank web part page...
When you insert the custom list form this time, choose "Display item form"
All we have to do on this one is create a conditional formatting rule that will show the content IfHasRights(16)
NOW, it's time to save each of these data views as web parts. Go to the browser, and navigate to the library where you saved the 3 web part pages you just created. Open each page export the web part. Save the *.webpart files to your desktop or whatever. In the filename, be sure to indicate whether it's New, Edit, or Display.
In your Policies list, create 3 new, standard views, and call them "New", "Edit", and "Disp".
On each of these new views:
- click <site actions> and <edit page>. Delete the default list view web part. Be sure to delete it, not just close it.
- Import the associated web part from your desktop.
- Exit Edit Mode
Now that there are 3 new forms in the Policies list, the last thing to do is associate them correctly. (I think that's the right terminology). Anyway, go back to SharePoint Designer.
In the left pane, under the Lists folder, right click on the Policies list, and choose "Properties".
Click the "Supporting Files" tab. Change the content type to Item.
Change each of the 3 supporting files to your new Edit, Display, and New aspx files.
Fun! Now test it!
Once it's just the way you like it, then you can delete those 3 original web part pages that you exported from. Check it out, we didn't leave anything unghosted!
Thanks,
Rajesh Batchu,
Share Point Developer,
Desk # :+1 409 945 1295
GV # :+1 23456 4 234 8
Mobile# :+1 40 9692 9692
